anchor.diff:  <?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>
   ----
   
  +NOTE: If you get a 404 or any other error, wait for a little longer until the containers are started up.
  +
   Lets stop the previously running container as:
   
   [source, text]
   ----
   docker stop mywildfly-mysql
   ----
  -
  
positive.code: +
  `-e` define environment variables that are read by the database at startup and allow us to access the database with this user and password.
  +
  . Start WildFly and deploy Java EE 7 application as:
  +
  [source, text]
  ----
  
negative.code: <<JavaEE7_PreBuilt_WAR>> explained how to use an in-memory database with the application server. This gets you started rather quickly but becomes a bottleneck soon as the database is only in-memory. This means that any changes made to your schema and data are lost when the application server shuts down. In this case, you need to use a database server that resides outside the application server. For example, MySQL as the database server and WildFly as the application server.
  
  .Two Containers On Same Docker Host
  image::images/javaee7-hol-container-linking.png[]
  
  This section will show how https://docs.docker.com/userguide/dockerlinks/[Docker Container Linking] can be used to connect to a service running inside a Docker container via a network port.
  
  