views:

2388

answers:

2

JBoss 5 has just come out of beta after 2 years, giving us a JEE 5 compliant container... several months before the release of JEE 6 (JavaOne in May or thereabouts 2009). We've had Glassfish v2 for awhile and now have Glassfish v3 Prelude.

Is there any reason to JBoss 5 over these? I've had the feeling for the last year or more than JBoss is essentially a dead project.

What do you think?

+5  A: 

JBoss is by no means a dead project; it is very active and has strong commercial backing from RedHat. They spent a significant amount of time redesigning the entire app server to run off the new JBoss Microcontainer. Not sure if it was worth the 3+ year effort but the release notes are here:

http://sourceforge.net/project/shownotes.php?release_id=645033&group_id=22866

As with any big rewrite of an app server, I would tread carefully on JBoss 5. If you are programming simply to Java EE specs then Glassfish will probably suit your needs fine. If you want to use parts of the JBoss stack (Seam, JBoss AOP, etc) then it might be worth targeting either JBoss 4 instead of 5 depending on your QA / deployment timeline. By the time 5.1 comes out, the major bugs should be fixed and you should hopefully be able to migrate easily then.

cliff.meyers
A: 

If your planning to use JMS be careful as connecting to JMS providers like IBM MQ can be a nighmare with glassfish.

As well as features you should consider how well it fits with the rest of your stack.

Karl

Karl
I'm interested to hear more about Glassfish issues with IBM MQ.
cletus