WildFly

From Wikipedia, the free encyclopedia
  (Redirected from Jboss)
Jump to: navigation, search
WildFly
Wildfly logo.png
Original author(s) JBoss
Developer(s) Red Hat
Stable release 8.0.0.Final / February 11, 2014 (2014-02-11)[1]
Preview release 8.0.0.Final / February 11, 2014 (2014-02-11)[2]
Written in Java
Operating system Cross-platform
Type Application server
License GNU Lesser General Public License
Website www.jboss.org/jbossas www.wildfly.org

WildFly,[3] 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.

The renaming to WildFly was done to reduce confusion. The renaming only affects the JBoss Application Server project. The JBoss Community or the Red Hat JBoss product line (with JBoss Enterprise Application Platform) all retain their names.[4]

Origin[edit]

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 EJB trademark within its name. EJB-OSS was then renamed to JBOSS, then JBoss later.[5] .

Versions[edit]

JBoss AS 4.0, a Java EE 1.4 application server, features an embedded Apache Tomcat 5.5 servlet container. It supports any Java Virtual Machine (JVM) between versions 1.4 and 1.6. JBoss can run on numerous operating systems including many POSIX platforms (like GNU/Linux, FreeBSD and Mac OS X), Microsoft Windows and others, as long as a suitable JVM is present.

JBoss AS 4.2 also functions as a Java EE 1.4 application server, but deploys Enterprise JavaBeans 3.0 by default. It requires the Java Development Kit version 5, and includes Tomcat 5.5.

JBoss AS 5.1, released in 2009, operates as a Java EE 5 application server. It is 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.[6] JBoss AS 5.1 contains a preview of some elements from the Java EE 6 specification.[7]

JBoss AS 6.0,[8] an unofficial implementation of Java EE 6, was released on December 28, 2010. Although JBoss AS 6 does not support the full Java EE 6 stack,[9] it chose not to support this officially[10][11] by obtaining an official certification from Oracle. It does, however, officially support the Java EE 6 Web Profile.

JBoss AS 7,[1] was released on July 12, 2011, only six months after the last major release, JBoss AS 6. Unlike previous increments of the major versioning number, JBoss AS 7 supports the same Java EE specification as the last major release, namely Java EE 6. The Java EE profile is only partially implemented in JBoss AS 7, e.g. it includes MDBs, but listening to JMS destinations (which is mandated by the full spec) is not supported.[12] It is, however, certified for the Web Profile. The software code has been completely rewritten for JBoss AS 7.[13][14] Major changes visible to the user are the inability to define resources like JMS destinations and datasources inside archives (war/ear),[15][16] the way datasources are defined,[17][18] a much smaller size (less than half of JBoss AS 6)[1] and a 10-fold reduction in startup time.[19]

JBoss AS 7.1, was released in February 2012. The remaining parts of the EE spec were implemented, and this version was certified for the EE full profile.[20]

WildFly 8 is the direct continuation to the JBoss AS project. WildFly 8.0.0 Final stable release was officially released February 11, 2014.[21]

Product features[edit]

Licensing and pricing[edit]

JBoss 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[edit]

Notes[edit]

References[edit]

External links[edit]