anchor.diff:  allows developers to quickly deploy an A-MQ message broker in a hybrid
   cloud environment.
   
  -However, there are significant differences in supported configurations and 
  +However, there are significant differences in supported configurations and
   functionality in the JBoss A-MQ image
   compared to the regular release of JBoss A-MQ. Documentation for other
   JBoss A-MQ functionality not specific to the JBoss A-MQ xPaaS image can
  
positive.code: 
  *JWS*
  
  * Tomcat's access log valve logs to file in container instead of
  stdout.:
  https://issues.jboss.org/browse/CLOUD-57[https://issues.jboss.org/browse/CLOUD-57]‌
  +
  Due to this issue, the logging data is not available for the central
  logging facility. To workaround this issues, use the `oc exec` command to
  get the contents of the log file.
  
  * `mvn clean` in JWS STI can fail:
  https://issues.jboss.org/browse/CLOUD-153[https://issues.jboss.org/browse/CLOUD-153]
  +
  It is not possible to clean up after a build in JWS STI because the
  Maven command `mvn clean` fails. This command fails due to Maven not being
  able to build the object model during startup.
  +
  To work around this issue, add Red Hat and JBoss repositories into
  *_pom.xml_* of the application if the application uses dependencies from
  there.
  
  * Datasource realm configuration is incorrect for JWS:
  https://issues.jboss.org/browse/CLOUD-156[https://issues.jboss.org/browse/CLOUD-156]
  +
  It is not possible to do correct JNDI lookup for datasources in the
  current JWS image if an invalid combination of datasource and realm
  properties is defined. If a datasource is configured in the *_context.xml_*
  file and a realm in *_server.xml_* file, then the *_server.xml_*'s
  `*localDataSource*` property should be set to true.
  
  *EAP*
  
  * JPA application fails to start when the database is not available:
  https://issues.jboss.org/browse/CLOUD-61[https://issues.jboss.org/browse/CLOUD-61]
  +
  JPA applications fail to deploy in EAP OpenShift Enterprise 3.0 image if
  an underlying database instance that the EAP instance relies on is not
  available at the start of the deployment. The EAP application tries to
  contact the database for initialization, but because it is not available,
  the server starts but the application fails to deploy.
  +
  There are no known workarounds available at this stage for this issue.
  
  * Continuous HornetQ errors after scale down " Failed to create netty
  connection":
  https://issues.jboss.org/browse/CLOUD-158[https://issues.jboss.org/browse/CLOUD-158]
  +
  In the EAP image, an application not using messaging complains about
  messaging errors related to HornetQ when being scaled.
  +
  Since there are no configuration options to disable messaging to
  workaround this issue, simply include the file *_standalone-openshift.xml_*
  within the source of the image and remove or alter the following lines
  related to messaging:
  +
  ----
  Line 18:
  
negative.code: release of JBoss EAP. To learn about these differences, please read
  link:../using_images/xpaas_images/eap.html[this documentation].
  Documentation for other JBoss EAP functionality not specific to the
  JBoss EAP xPaaS image can be found in the
  https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/[JBoss EAP documentation on the Red Hat Customer Portal].
  
  === xPaaS Image for Red Hat JWS
  