anchor.diff:  
   Only two changes are required to the standard `jboss/wildfly` image:
   
  -. Start WildFly in full platform:
  +. By default, WildFly starts in Web platform. This Java EE 7 application uses some capabilities from the Full Platform and so WildFly is started in that mode instead as:
   +
   [source, text]
   ----
   CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone-full.xml", "-b", "0.0.0.0"]
   ----
   +
  -. WAR file is copied to `standalone/deployments` directory as:
  +. WAR file is copied to the `standalone/deployments` directory as:
   +
   [source, text]
   ----
  -RUN curl -L https://github.com/javaee-samples/javaee7-hol/blob/jrebel/solution/movieplex7-1.0-SNAPSHOT.war?raw=true -o /opt/jboss/wildfly/standalone/deployments/movieplex7-1.0-SNAPSHOT.war
  +RUN curl -L https://github.com/javaee-samples/javaee7-hol/raw/master/solution/movieplex7-1.0-SNAPSHOT.war -o /opt/jboss/wildfly/standalone/deployments/movieplex7-1.0-SNAPSHOT.war
   ----
  
positive.code: 
  [source, text]
  ----
  docker pull classroom.example.com:5000/javaee7-hol
  ----
  
  The javaee7-hol link:https://github.com/arun-gupta/docker-images/blob/master/javaee7-hol/Dockerfile[Dockerfile] is based on `jboss/wildfly` and adds the movieplex7 application as war file.
  
  Run it as:
  
  [source, text]
  ----
  docker run -it -p 8080:8080 classroom.example.com:5000/javaee7-hol
  ----
  
  See the application in action at http://dockerhost:8080/movieplex7/.
  
  This uses an in-memory database with WildFly application server as shown in the image:
  
  
negative.code: [[JavaEE7_PreBuilt_WAR]]
  ## Deploy Java EE 7 Application (Pre-Built WAR)
  
  https://github.com/javaee-samples/javaee7-hol[Java EE 7 Movieplex] is a standard multi-tier enterprise application that shows design patterns and anti-patterns for a typical Java EE 7 application.
  
  .Java EE 7 Application Architecture
  image::../images/javaee7-hol.png[]
  