Why GlassFish over JBoss ?
discussion happened on
Forums where a user asked for pros/cons for GlassFish vs JBoss. A
explained his reasons to choose GlassFish over JBoss. Here are they key
- Admin GUI and CLI alone are true differentiators.
- Java EE5 with EJB3 is much better to work with and GlassFish is JavaEE5
compatible, of course it's the Reference Implementation as well.
- Seamless integration with NetBeans.
- Solid and consolidated documentation.
- "overall GF is just plain easier to use and that's my major pain
- "The new clustering looks spectacular"
- "GF is really a joy to work with and we haven't had any major
problem using it"
- "you will be up to speed and productive more quickly on GF than
JBoss, and just as important, you will stay that way"
- "because of JEE 5, EJB3, and the JPA, and leveraging that
technology, our applications run better, and are easier to maintain. GF is
not the sole perveyor of such technology, but the combination and
integration of the whole thing: GF, NB, EJB3, and the low learning curve and
overall ease of use makes the entire package a "performance win" for our
apps as is"
- "The best part is the server is handling more and more of the
stuff we need to do and we have to work around it less and less."
And if these are not enough for you to choose GlassFish, here is a more
detailed list of
Use GlassFish ?.
And we see GlassFish as "GlassFish is WebLogic Features and Performance at
JBoss's price" except we are shooting for better Features and Performance than