WildFly

WildFly
Original author(s) JBoss
Developer(s) Red Hat
Stable release
10.1 / August 19, 2016 (2016-08-19)
Repository github.com/wildfly/wildfly
Written in Java
Operating system Cross-platform
Type Application server
License GNU Lesser General Public License
Website www.wildfly.org

WildFly,[1] formerly known as JBoss AS, or simply JBoss, is an application server authored by JBoss, now developed by Red Hat. WildFly is written in Java, and implements the Java Platform, Enterprise Edition (Java EE) specification. It runs on multiple platforms.

WildFly is free and open-source software, subject to the requirements of the GNU Lesser General Public License (LGPL), version 2.1.

On 20 November 2014, JBoss Application Server was renamed WildFly. The JBoss Community and other Red Hat JBoss products like JBoss Enterprise Application Platform were not renamed.[2]

Origin

In 1999, Marc Fleury started a free software project named EJB-OSS (stands for Enterprise Java Bean Open Source Software) implementing the EJB API from J2EE (Java 2 Enterprise Edition). Sun Microsystems asked the project to stop using the trademarked EJB within its name. EJB-OSS was then renamed to JBOSS, then JBoss later.[3]

Versions

This list is incomplete; you can help by expanding it.
Product version Java EE version Release to web Description
0.0.4 ? 24 February 1999 Early access release
2.2 1.2 ?
2.4 1.2 ? Integration with Tomcat 3.2
3.0 "Rabbit Hole" 1.3 31 May 2002
3.2 1.3 2 June 2003
4.0 1.4 20 September 2004 v4.0 features an embedded Apache Tomcat 5.5 servlet container, and supports any Java Virtual Machine (JVM) versions 1.4 through 1.6.
4.2 1.4 11 May 2007 Deploys Enterprise JavaBeans 3.0 by default. It requires the Java Development Kit version 5, and includes Tomcat 5.5.
5.1 5.0 23 May 2009 A minor update of the major release JBoss AS 5.0, which was in development for at least three years and was built on top of a new JBoss microcontainer.[4] JBoss AS 5.1 contains a preview of some elements from the Java EE 6 specification.[5]
6.0[6] 6.0 28 December 2010 Although JBoss AS 6 does support the full Java EE 6 stack,[7] Red Hat elected not to certify it with Oracle[8][9] It is, however, officially certified to support the Java EE 6 Web Profile.
7.0[10] "Lightning" 6.0 12 July 2011 The Java EE profile is only partially implemented: It includes MDBs, but listening to JMS destinations is not supported.[11] It is, however, certified for the Web Profile. The software code has been completely rewritten for JBoss AS 7.[12][13] Major changes visible to the user are the inability to define resources like JMS destinations and datasources inside archives (war/ear),[14][15] the way datasources are defined,[16][17] a much smaller size (less than half of JBoss AS 6)[10] and a 10-fold reduction in startup time.[18]
7.1 6.0 16 February 2012 Red Hat implemented the remaining parts of the EE spec, and this version was certified for the EE full profile.[19]
8.0.0 7.0 20 November 2014[20] JBoss renamed to WildFly. Undertow replaced JBossWeb as web container
9.0.0 "Kenny" 7.0 2 July 2015[20] WildFly/WildFly Core split.
10.0.0 7.0 9 February 2016[20] Java 8+ support (Java 7 support discontinued), ActiveMQ Artemis, HA Singleton Deployments, HA Singleton Message Driven Beans (MDBs) and MDB Delivery Groups, Stateless Session Bean and Message Driven Bean Automatic Pool Sizing, Hibernate 5
10.1.0 7.0 19 August 2016[20]

Upgrades to newer versions of WildFly or JBoss EAP may be handled using the JBoss Windup migration tool.[21]

Product features

Licensing and pricing

JBoss EAP itself is open source, but Red Hat charges to provide a support subscription for JBoss Enterprise Middleware. Before November 2010 JBoss was licensed as annual subscription in bundles of 4 and 32 CPU sockets. As of November 2010 the licensing changed and all cores on the system are now counted. The core bundles licensing is available for 16 and 64 cores.[22]

See also

Notes

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.