Jump to content

WildFly

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Falsodar (talk | contribs) at 13:08, 14 April 2015 (update 9.0.0.Beta2, other cleanup). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

WildFly
Original author(s)JBoss
Developer(s)Red Hat
Stable release
8.2.0.Final / November 20, 2014 (2014-11-20)[1]
Preview release
9.0.0.Beta2 / March 27, 2015 (2015-03-27)[1]
Repository
Written inJava
Operating systemCross-platform
TypeApplication server
LicenseGNU Lesser General Public License
Websitewww.jboss.org/jbossas
www.wildfly.org

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

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

Versions

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.[5] JBoss AS 5.1 contains a preview of some elements from the Java EE 6 specification.[6]

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

JBoss AS 7,[11] 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)[11] 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 November 20, 2014.[21]

Product features

Screenshot of Wildfly server on an Android tablet phone.

Licensing and pricing

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

Notes

  1. ^ a b ""Downloads · WildFly"". Cite error: The named reference "Downloads · WildFly" was defined multiple times with different content (see the help page).
  2. ^ "JBoss Application Server has a new name... WildFly". Retrieved 2013-04-23.
  3. ^ "Frequently Asked Questions About WildFly". Retrieved 2013-04-23.
  4. ^ Jamae, Javid; Johnson, Peter (2009-01-20). "1.1 Introducing JBoss". JBoss in Action: Configuring the JBoss Application Server. Manning Publications. p. 4. ISBN 978-1-933988-02-3. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help)
  5. ^ "JBossAS 5.0.0.GA Released". 2008-12-05.
  6. ^ "JBoss 5.1.0.GA Release Notes". 2009-05-23.
  7. ^ "Home / JBoss / 6.0.0.Final". JBoss Community. 2010-12-28.
  8. ^ http://community.jboss.org/thread/160813
  9. ^ http://dandreadis.blogspot.com/2011/01/introducing-brand-new-jboss-as-60.html
  10. ^ http://community.jboss.org/message/574581
  11. ^ a b Cite error: The named reference JBoss_downloads was invoked but never defined (see the help page).
  12. ^ http://community.jboss.org/thread/169508
  13. ^ http://community.jboss.org/message/595453
  14. ^ http://planet.jboss.org/post/why_is_jboss_as_7_so_fast
  15. ^ http://community.jboss.org/message/606449
  16. ^ http://community.jboss.org/wiki/JBossAS7VsAS6
  17. ^ http://community.jboss.org/wiki/DataSourceConfigurationInAS7
  18. ^ How to create and manage datasources in AS7
  19. ^ JBoss Application Server 7.
  20. ^ http://planet.jboss.org/post/jboss_as_7_1_0_final_thunder_released_java_ee_6_full_profile_certified
  21. ^ Cite error: The named reference wildfly.org was invoked but never defined (see the help page).
  22. ^ "JBOSS NA Channel SKUs: Production Subscription SKUs". Red Hat.

References