WildFly 10: New main version of Java EE 7 application server is now available
After much anticipation, WildFly 10 is now available for download. It features plenty of new capabilities and improvements.
The tenth main version of the open source Java EE application server WildFly is now available for download. WildFly 10 includes WildFly 9’s major features (HTTP/2 support, built in load-balancer), but it also has some new capabilities.
New capabilities and improvements
Java 7 support has been discontinued in order to allow a deeper integration with the Java 8 runtime. Another addition is the support of the Java 9 snapshots, which have been available to date. Moreover, the HornetQ project has been fully replaced by the ActiveMQ Artemis in WildFly 10. The collaboration between the development teams of HornetQ and ActiveMQ can be seen in the new JMD broker, which includes a plethora of new features. It also retains protocol compatibility with the former broker.
Another feature that can be found in WildFly 10 is the Undertow JS project, which allows you to write server side scripts that can pull in CDI beans and JPA Entity Beans. Speaking of new elements, WildFLY 10 also sports a feature that existed in AS 6.0 and earlier. It adds the ability to deploy a given application as a “singleton deployment”. A singleton deployment will only deploy on a single node. If the node stops or fails, the deployment will automatically start on another node.
There is also a set of management operations that can convert old configuration over to the new respective subsystem equivalent. This is especially helpful for users who want to migrate from an old subsystem such as jbossweb (AS 7.1), jacorb (WildFly 8) or hornetq (WildFly 9). Old CLI scripts as well as custom provisioning systems can also benefit from these operations.
The support of Hibernate 5 is also on the list of new additions, as well as Powershell Scripts. The latter’s purpose is to fully replace .bat scripts in future releases. Although they provide the same functionality, they address a handful of issues found in batch scripts.
A more detailed description can be found in the release notes.