JBoss: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
(18 intermediate revisions by the same user not shown)
Line 2: Line 2:
=Disambiguation=
=Disambiguation=


WildFly is the community edition JBoss. Enterprise Application Platform (EAP) is the subscription-backed enterprise version JBoss. Both of them are built in top of a "JBoss" code base: the package names start with "org.jboss", the Java system properties start with "org.jboss", etc. The management scripts refer to "JBOSS_HOME" and other JBOSS* environment variables, in both cases. <font color=red>Not sure about this, keep thinking about it: Operationally, it is best if we refer to an instance specifically as "WildFly" and "EAP", and avoid mentioning to them as "JBoss".</font>
WildFly is the community edition JBoss. Enterprise Application Platform (EAP) is the subscription-backed enterprise version JBoss. Both of them are built in top of a "JBoss" code base: the package names start with "org.jboss", the Java system properties start with "org.jboss", etc. The management scripts refer to "JBOSS_HOME" and other JBOSS* environment variables, in both cases. However, we feel that in the future "JBoss" labeling will increasingly fade from the forefront, so this knowledge base will attempt to refer to everything JBoss as either WildFly or EAP.


=Flavors=
=Flavors=
* [[WildFly]]
* [[WildFly]]
* [[EAP]]
* [[EAP]]
=Subjects=
* [[JBoss Convenience Aliases]]
* [[JBoss System Properties]]
* [[JBoss Isolated Self-Contained Standalone Profile]]
* [[XNIO]]
* [[Maven Repository-Based JBoss IntelliJ Investigation Environment]]

Latest revision as of 20:24, 29 April 2016

Disambiguation

WildFly is the community edition JBoss. Enterprise Application Platform (EAP) is the subscription-backed enterprise version JBoss. Both of them are built in top of a "JBoss" code base: the package names start with "org.jboss", the Java system properties start with "org.jboss", etc. The management scripts refer to "JBOSS_HOME" and other JBOSS* environment variables, in both cases. However, we feel that in the future "JBoss" labeling will increasingly fade from the forefront, so this knowledge base will attempt to refer to everything JBoss as either WildFly or EAP.

Flavors