Clever Geek Handbook

Any reason to use JBoss 5 over GlassFish v2 / v3 Prelude?

JBoss 5 just came out of beta after 2 years, providing us with a Java EE 5 compatible container months before the release of Java EE 6 (JavaOne in May or around 2009). We already have GlassFish v2 and now we have GlassFish v3 Prelude.

Are there any reasons for JBoss 5? I had a feeling that in the past year or more, JBoss is essentially a dead project.

What do you think?

+4


source to share


2 answers


JBoss is by no means a dead project; he is very active and has strong commercial support from RedHat. They spent a significant amount of time redesigning the entire application server to launch 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 application server rewrite, I'd keep a careful eye on JBoss 5. If you're programming just the Java EE specs, Glassfish will probably meet your needs. If you want to use parts of the JBoss stack (Seam, JBoss AOP, etc.) then it might be worth targeting JBoss 4 instead of 5 depending on your QA / deployment timeline. By the time 5.1 comes out, major bugs should be fixed and you can hopefully be able to migrate easily.

+5


source


If you plan on using JMS, be careful, as the connection to JMS providers like IBM MQ can be glassfish non-blinking.

As with functions, you should think about how well it fits into the rest of your stack.



Charles

0


source






More articles:


All Articles