JBoss: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
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. Operationally, it is best if we refer to an instance specifically as "WildFly" and "EAP", and avoid mentioning to them as "JBoss". In the light of this suggestion, convenience aliases are different for WildFly ([[WildFly Convenience Aliases|WildFly convenience aliases]]) and EAP ([[EAP Convenience Aliases|EAP convenience aliases]]). | 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". In the light of this suggestion, convenience aliases are different for WildFly ([[WildFly Convenience Aliases|WildFly convenience aliases]]) and EAP ([[EAP Convenience Aliases|EAP convenience aliases]]).</font> | ||
=Flavors= | =Flavors= | ||
* [[WildFly]] | * [[WildFly]] | ||
* [[EAP]] | * [[EAP]] |
Revision as of 07:47, 8 January 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. 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". In the light of this suggestion, convenience aliases are different for WildFly (WildFly convenience aliases) and EAP (EAP convenience aliases).