This content has been marked as final.
Show 6 replies
-
1. Re: comparative study of Jonas / Jboss / Glassfish / Geronim
dimitris Mar 11, 2009 1:14 PM (in response to aldian_00)Which new technologies are you interested (integrating) in?
-
2. Re: comparative study of Jonas / Jboss / Glassfish / Geronim
aldian_00 Mar 12, 2009 4:44 AM (in response to aldian_00)I am very interested in JMS load balancing and EJB load balancing.
-
3. Re: comparative study of Jonas / Jboss / Glassfish / Geronim
dimitris Mar 13, 2009 8:56 AM (in response to aldian_00)Don't we have those already? You may ask in the specific EJB and JBoss Messaging forums if you want help.
-
4. Re: comparative study of Jonas / Jboss / Glassfish / Geronim
aldian_00 Mar 16, 2009 9:00 AM (in response to aldian_00)But what I am asking in this topic is not about specifically EjB and JMS, but about what you think of this comparative array: http://forums.java.net/jive/servlet/JiveServlet/download/56-58417-336265-7930/comparative_array.PNG
-
5. Re: comparative study of Jonas / Jboss / Glassfish / Geronim
henk53 Apr 4, 2009 6:39 AM (in response to aldian_00)"Aldian_00" wrote:
But what I am asking in this topic is not about specifically EjB and JMS, but about what you think of this comparative array: http://forums.java.net/jive/servlet/JiveServlet/download/56-58417-336265-7930/comparative_array.PNG
I think it sums it up nicely. Geronimo may be nice in theory, but in practice it's largely irrelevant since absolutely nobody actually uses it. Jboss has indeed been slow to adapt new features in the past, but maybe this is going to change for Java EE 6?
For Glassfish you mention that it has very complex configuration files. I don't think this is true as it is said that Glassfish can simply not be configured at all. The major disadvantage for Glassfish should thus be: "Can't be configured".
Another major disadvantage is that Glassfish doesn't offer any services, while Jboss of course does. You mention this a little with "excellent load balancing possibilities" for Jboss, but I would make it more explicit: "Wide number of services: load balancing, url deployment, etc". For Glassfish the disadvantage would be : "Offers absolutely no services (runs a bare JSF page and that's about it)".
An advantage that you really have to add to Glassfish though is that it implements new Java EE features incredibly fast. It is expected that Glassfish will be Java EE 6 certified only weeks after the release of the spec, while with Jboss we *may* be looking at atleast 1, possibly 2 years for that to happen. (this is my personal guess, perhaps someone from Jboss can give a more accurate estimate) -
6. Re: comparative study of Jonas / Jboss / Glassfish / Geronim
dimitris Apr 5, 2009 4:56 AM (in response to aldian_00)Well, expect JBoss to be certified for EE6 a lot faster, this time.
EE5 took longer than expected due to the change in kernel, not because the EE5 spec, which 95% of it was already implemented in JBoss 4.2.