anchor.diff:  to install and rollback new static modules and binary files using the
   WildFly management protocol.
   
  -Notable Updates Since Alpha4
  -~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  +Simplified & Improved EJB Clustering
  +------------------------------------
  +When using the HA profiles, all EJBs support clustering capabilities. More specifically they
  +are no longer required to be annotated with @Clustered. Also clustering now utilizes 
  +Infinispan 6 capibilities in a more efficient manner, which reduces the overhead involved
  +with clustered applications.
   
  -* Initial EE Batch support
  +Improved JDK8 Compatibility
  +---------------------------
  +This release has improved compatibility with JDK8, and we now encourage everyone interested
  +in Java 8 to run WildFly 8 on it as well. Expect future releases of WildFly to include APIs that
  +take advantage of the new language features.
   
  -* Initial EE concurrency support
  +
  +Other Updates Since Beta1
  +~~~~~~~~~~~~~~~~~~~~~~~~~
  +
  +* Logging now supports custom formatters
  +
  +* CDI integration and performance improvements
   
   * Java EE Connector Architecture 1.7 support
   
  
positive.code: For those unfamiliar with Java EE7, it is an industry leading specification that offers
  applications productivity improving capabilities, including support for the modern web, 
  batch processing, and improvements in dependency injection. 
  
  More Port Reduction
  -------------------
  HornetQ, our JMS implementation, is now multiplexed over HTTP, which fully completes our port
  reduction goals for WildFly 8.
  
  By utilizing HTTP upgrade, WildFly 8 has moved nearly all of its protocols to be multiplexed 
  over two HTTP ports: a management port, and an application port.  This is a big benefit to 
  cloud providers (such as OpenShift) who run hundreds to thousands of instances on a single 
  server. Our default configuration now only has _three_ ports, and *_will become 
  two ports by final._* We decided to preserve the original, now duplicative, native management port once again in 
  this release to remove any potential obstacle in evaluating the release. 
  
  Simplified & Improved EJB Clustering
  ------------------------------------
  When using the HA profiles, all EJBs support clustering capabilities. More specifically they
  are no longer required to be annotated with @Clustered. Also clustering now utilizes 
  Infinispan 6 capibilities in a more efficient manner, which reduces the overhead involved
  with clustered applications.
  
  Improved JDK8 Compatibility
  ---------------------------
  This release has improved compatibility with JDK8, and we now encourage everyone interested
  in Java 8 to run WildFly 8 on it as well. Expect future releases of WildFly to include APIs that
  take advantage of the new language features.
  
  Logging Improvements
  --------------------
  
  
  High Performance Web Server (http://undertow.io/[Undertow.io])
  
negative.code: implement nearly anything from dynamic request routing to custom
  protocols. It can also function as a very efficient, pure non-blocking
  reverse proxy, allowing WildFly to delegate to other web servers with
  minimal impact to running applications. This release adds numerous
  improvements including greater extensibility and enhanced security 
  capabilities.
  
  
  Port Reduction
  --------------
  By utilizing HTTP upgrade, WildFly 8 has moved nearly all of its protocols to be multiplexed 
  over two HTTP ports: a management port, and an application port.  This is a big benefit to 
  cloud providers (such as OpenShift) who run hundreds to thousands of instances on a single 
  server.  As of this release, HornetQ, our JMS implementation, is now multiplexed over HTTP, 
  which fully completes our port reduction goals for WildFly 8.
  
  In total, our default configuration now only has _three_ ports, and *_will become 
  two ports by final._* We decided to preserve the original, now duplicative, native management port once again in 
  this release in order to remove any potential obstacle in evaluating the release. 
  
  Management Role Based Access Control (RBAC) & Auditing
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  