What’s Happening With JBoss?


UPDATE (Aug 2012) – The officially supported JBoss EAP 6.0 is finally released.  People using the supported EAP version will have much less confusion and one of the goals of this article was to clear up confusion about what is happening with the open source and EAP versions and how they relate.

If you are going to be using the latest versions of JBoss training is really a requirement because there are LOTS of changes (for the better) and you might need to reinvent somewhat how you approach management of JBoss in various job roles.  Training will help get you there faster and spend less time trying to figure out the new platform.

 

One thing that I’ve found to be true for enterprise clients is people don’t always have time to keep up with what is going on in the cutting edge of technology because they are busy just trying to keep up with their own responsibilities.  Since we have a lot of clients that use JBoss I figure I would help bring everybody “up to speed” with what is happening with JBoss on the Java EE front.  There have been several developments recently and there will be more over the next several months.

The first thing to determine is what “edition” of JBoss you are talking about.  Ultimately this comes down to if you are paying RedHat/JBoss for a support subscription to access the “officially supported” version of JBoss.  This “officially supported” version of JBoss is the JBoss Enterprise Application Platform (JBoss EAP).  If you are not paying for a support subscription you are likely using the “free, open-source” version of JBoss Application Server (JBoss AS).

So what is the difference between the two?  Although these are both “JBoss” editions there are some important differences:

  • The JBoss EAP contains some version of JBoss AS.  You can find the relationship between the released versions here.
  • These editions are released at different times with JBoss EAP released sometime after the version of JBoss AS it contains.
  • The versions of these two JBoss “editions” do not often match.  They did match somewhat with JBoss 5.x but they do not match now.  More on this in a second.
  • The JBoss EAP is the only version that will often have bug fixes back-ported to older versions.  JBoss AS “may” have bug fix releases but it is often only applying bug fixes to the “next” version of JBoss AS.  If it is important to have bugs fixed in JBoss without moving to a new JBoss version or you compiling JBoss source code updates yourself the JBoss EAP is a great investment.
  • A JBoss EAP subscription includes access to the JBoss Operations Network which is a great product for managing and monitoring several JBoss servers.
  • The JBoss EAP includes and is verified against specific versions of other popular libraries like Hibernate and JBoss Seam.  Often fixes released to the JBoss EAP will include critical fixes for these included libraries also.  What versions of particular libraries are included is listed here.
  • The different versions of JBoss EAP and JBoss AS will be compliant and “certified” against different versions of Java Enterprise (Java EE).  This will be especially important for Java EE 6 as discussed next.

Current/Upcoming JBoss Versions

  • JBoss AS 5.1
  • JBoss EAP 5.1 – includes JBoss AS 5.1 internally
  • JBoss AS 6.0/6.1 – Not major internal changes although some changes in web service stack and JMS stack.  Good summary here. Will never be released as part of a supported JBoss EAP version.
  • JBoss AS 7.0 – Final/GA release available. Significant internal and administrative changes compared to JBoss AS 6.x.
  • JBoss AS 7.1 – Beta release available, not yet GA/Final. Significant internal and administrative changes compared to JBoss AS 6.x.
  • JBoss EAP 6.0 – not yet released (early 2012?). Will include JBoss AS 7.1 internally

JBoss AS Downloads

JBoss EAP Information

Java EE 6 Certification

The other thing that causes some issues right now is what it means to be “Java EE Certified” for Java EE 6.  Java EE 6 introduced the concept of “profiles” so that Java EE servers could be certified against a subset of the Java EE specifications but not against the “full profile” of all specifications.  This is important because some Java EE technologies like EJB 2.x Entity EJBs are on their way out anyway now that we have modern replacements like Java Persistence (JPA).  The only profile that Java EE 6 defined besides the “full profile” is the “Java EE 6 Web Profile”.

The following are some of the highlights of the Java EE 6 Web Profile (not a complete list but the major things):

  • Servlet 3.0
  • JSP 2.2
  • JSF 2.0
  • JPA 2.0
  • Contexts and Dependency Injection for the Java EE Platform 1.0 (CDI)
  • EJB 3.1 “Lite” (This includes basically only non-remote Session EJBs)

There are some significant technologies that are in the “full profile” but NOT required in the “Web Profile” (not a complete list but the major differences):

  • JMS
  • Web Services (JAX-WS, JAX-RS “RESTful”, and JAX-RPC)
  • All of EJB 3.1 (including 2.x Entity EJBs, Message Driven EJBs, EJB Timer)
  • JavaMail

So servers that are certified against the “Java EE 6 Web Profile” are only “required” to have a subset of Java EE 6 technologies.  Now most of the JBoss AS versions offer technologies above and beyond the Web Profile but JBoss AS 7.1 (which will be included in JBoss EAP 6.0) is the only version that will target certifying against the “Full” Java EE 6 profile.  There is a good discussion here about exactly what it means (for JBoss AS 6.x anyway) to have been tested against the Java EE 6 web profile but also offer additional technologies.  It is also interesting to note that in the downloads of JBoss AS there is a download for JBoss AS 7.0.x which is “Web Profile Only” and has been officially certified for Java EE 6 by Oracle and there is an “Everything” download which has additional technologies but is specifically advertised as not being officially certified.

JBoss Versions and Java EE Certification

  • JBoss AS 5.1 – Java EE 5 Certified
  • JBoss EAP 5.1 – Java EE 5 Certified
  • JBoss AS 6.0/6.1 – Not officially certified for Java EE 6 Web Profile but tested internally by JBoss against the web profile test suite
  • JBoss AS 7.0.x – Officially certified for Java EE 6 Web Profile. An “Everything” download available with more
  • JBoss AS 7.1.x – Will be certified against “Full Java EE 6 profile”. Good description of the strategy here.
  • JBoss EAP 6.0 – Will be certified against “Full Java EE 6 profile”. Good description of the strategy here.

JBoss Versions and Support/Bug Fixes

Finally, I think the other consideration that will be important to people when switching will be consideration of how they will deal with the inevitable problems/questions that come up and how confident they might be about the software being fixed with bugs.  For those that this issue is mission critical, I would again highly suggest looking into a subscription to the JBoss Enterprise Application Platform.  This is the only form of JBoss that will have a support service level agreement and where bugs will be backported to previous versions for several years according to the JBoss Enterprise Middleware support policy.

When using one of the JBoss AS releases the only “support” that is available is from the JBoss Community and any available JBoss AS Documentation.  For users of JBoss AS I think it is important to consider the level of support from the JBoss community since that support comes primarily from three sources:

  • Other JBoss users that may have similar issues/questions
  • JBoss AS developers working on the open source project
  • JBoss EAP staff working on support of JBoss EAP specifically

Of course this community support would also apply to clients of the JBoss EAP since it is based on a version of JBoss AS and would be useful above and beyond the normal “official” support available for JBoss EAP.

The other thing to consider is if there have been bug fix releases of the JBoss AS versions or not.

Thoughts on Level of Community Support/Bug Fix Releases for JBoss AS Versions

  • JBoss AS 5.1 – No bug fix releases.  Still lots of users using this version, JBoss AS developers not as active, JBoss EAP staff active as it is part of a supported JBoss EAP version.
  • JBoss AS 6.x – 6.1 is a bug fix release of 6.0 but is the only one.  Lots of users on this one based on downloads, JBoss AS developers and JBoss EAP staff not as active since this version is very different than JBoss AS 7.x and JBoss AS 6.x will never be part of a supported JBoss EAP release.
  • JBoss AS 7.x – This has already had two 7.0.x bug fix releases in only two months which is better than previous JBoss AS versions.  Lots of community activity from users and JBoss AS developers.  JBoss EAP staff also likely active getting ready to include JBoss AS 7.1 in JBoss EAP 6.0.

Conclusions

So where does this leave you as a JBoss user?  What version should you be using now or planning to move to?  Every situation is different based on different factors like:

  • Are you migrating existing applications or developing new applications?
  • Do you use technologies that are not required by the Java EE 6 Web Profile?
  • Do you have applications that depend only on the Java EE specifications or do they utilize internal JBoss infrastructure (like custom “JBoss SAR” or “Service Archives”)?
  • How much do you need to configure administratively outside of your deployed applications (EAR, WAR, etc) and how hard would it be to determine how to configure those in a new version?
  • How important is “Full Java EE 6” certification compared to “Java EE 6 Web Profile” certification for you?
  • How important is the support offered by JBoss EAP?
  • Is there some kind of deadline you are working under that might prevent you from waiting for JBoss AS 7.1 or JBoss EAP 6 and the certification of the full Java EE 6 profile that would bring?

Certainly without knowledge of your particular situation it would be unwise for me to offer any kind of direct suggestion here.  In general though I might be hesitant to use JBoss AS 6, at least for very long, as this is not getting the attention of as many from the JBoss AS developer or JBoss EAP support staff groups and JBoss has decided that they will not release it as part of any supported platform.  There is also some question about using anything like JBoss AS 6.0 or JBoss AS 7.0 which is not certified against the full profile but offers varying degrees of additional features between the two Java EE 6 profiles.

For those that might value stability and Java EE certification above all else, and who do not have to start using new Java EE 6 features on some tight deadline, I might hold out for JBoss AS 7.1 or JBoss EAP 6.0.  You could even start investigating that migration now with the release of JBoss AS 7.1.0.Beta1!

, ,

  1. #1 by Ondra Zizka on March 19, 2013 - 9:41 pm

    Similar, official info about AS 7 vs. EAP 6: http://www.jboss.org/jbossas/faq
    And now EAP is downloadable for free: http://www.jboss.org/jbossas/downloads .

  2. #2 by Ondra Zizka on March 19, 2013 - 9:42 pm

    BTW, is it still easier to run a blog site on PHP rather than Java EE 6? No offense, just interested.

  3. #3 by Stuart Smith on April 3, 2013 - 11:41 am

    Thanks for pointing this out. I’m not sure if I’m crazy about this or not as it adds confusion to the JBoss AS world even more than before. It would be nice if they listed where to get the latest nightly build of JBoss AS on the downloads page.

    There is some info on this here but hey seem to be building the JBoss AS 8 stream now.
    https://community.jboss.org/thread/167590

  4. #4 by Stuart Smith on April 3, 2013 - 11:45 am

    I’ve never tried to build a blog with either so I couldn’t say. I’m sure there are tons of PHP blog templates so the coding would mostly be done and it would be more about gathering images and editing CSS styles to look the way you want.

    I think the power of Java EE is that you have a lot of tools for all kinds of integration that might need to be done with various other systems and applications. Java EE 5/6 has added a lot of simplifying features from the community so now it is easier to do a lot of common things.

(will not be published)

*