WildFly

WildFly is the application server on the basis of the open code.

Screenshot of a window of administrative console (2015)

2016: Release of WildFly 10

On January 29, 2016 the Red Hat company provided release of the free WildFly 10 application server. The WildFly server is replacement to the free product JBoss Application Server, it is renamed into avoidance of confusion and intersection with a commercial product of JBoss Enterprise Application Platform and^[1].

Implementation is certified on compliance of Full-and to the Java EE 7 Web profiles. The WildFly code is distributed under the license LGPL.

Unlike a commercial product of JBoss Enterprise Application Platform positioned as completely tested and certified Java EE, WildFly platform it is focused, first of all, on promotion of technologies. WildFly acts as the upstream-project for a commercial product of JBoss Enterprise. As the main field of use WildFly development and rapid implementation of prototypes is considered.

Main features of release:

• Support of Java 7 is stopped that allowed to provide deeper integration with Java 8 Runtime. Support of the current snapshots Java 9 is added;
• Delivery of ActiveMQ Artemis as the broker of mailing of messages (Java Message Service Broker) compatible at the level of the protocol and HornetQ which replaced with itself;
• Start support a host controller by means of CLI. The new embed-host-controller command allows to edit contents of the domain.xml and host.xml files without start of additional processes or opening of network sockets;
• The support of JavaScript in the Undertow.io http-server allowing to create server scripts which can address to CDI Beans and JPA Entity Beans in the JavaScript language. It is convenient to use the specified opportunity for creation of external bindings or REST processors. The edited JavaScript code becomes available at once and does not demand restart the application;
• Support of single failsafe application deployment ("singleton deployment") at which in case of use of group of the clustered servers deployment will be made only on one node, but in case of an exit of this node out of operation, the application will be automatically postponed for other node;
• Support of the single fault-tolerant broker of mailing of messages (Singleton MDB) starting delivery only on one node, but in case of the failure using other node for message handling;
• The automatic choice of the size of a pool of SLSB and MDB, depending on the available system resources;
• Means for migration of outdated subsystems, such as jbossweb (AS 7.1), jacorb (WildFly 8) and hornetq (WildFly 9) which automate conversion of old configurations to the equivalents working in WildFly 10;
• In implementation of Hibernate 5 the quality of a bytecode is considerably improved, are entered optimization of performance and improvements in API are added.

Notes