If You Are An Java EE (at least EJB) Consultant - You Should Not Rely On Crisis To Have Vacations...
I actually thought this year will be quiet - because of the "crisis", and planned to write some articles, books, doing some research and just enjoying "hacking" some cool not-commercial stuff. My planning didn't worked out - I got even more contracts (plus the planned articles, conferences and books :-)) then the years before, what seems to be not logical at the first glance. I even had to cancel some conference events and JUG meetings, because of the workload (sorry for that - I hate to cancel things).
I asked some clients about this trend, and it turns out, that especially bigger companies tend to rely on standards during the economic downturn to be as much as possible vendor independent. In fact EJBs 3.0 are the only remaining, vendor independent, component model which is now supported by Glassfish, Geronimo, JBoss, SAP, Oracle WLS, IBM and probably many others.
The portability story is very good - in my last three Java EE 5 years all the project were tested on several servers and were absolutely portable (there is nothing more vendor specific - just a JAR). You can just move the application from one server to another copying the EAR - there is nothing more to do. The remaining issue is the quality of the application server, and especially the persistence itself - but this is always an issue.
I plan my vacations now in the next Web 3.0 wave then :-).
I will play Devil's Advocate: to Spring users, EJB's standards based portability is not an advantage over Spring because Spring runs on every application server too. The difference is the runtime is packaged into your .war instead of being provided by the application server.
Posted by Ryan on March 13, 2009 at 01:26 AM CET #
it is spelled "quiet" not "quite". Quite means something ...quite different!
Posted by Mr X on March 13, 2009 at 03:36 PM CET #
was a type - corrected that - thanks!
Posted by Adam Bien on March 13, 2009 at 07:40 PM CET #
Spring is very portable - it is actually an alternative stack. The point is only the support issue. If Spring runs on an appserver, you will need the support from the spring guys (beause of the changed release strategy) AND the appserver vendor (mainly because of political reasons). If you are relying on Java EE 5, you only need the support for the appserver. You don't need any additional frameworks library etc. And you can freely choose between the appserver vendors moving your application from one server to another,
thanks for your comment!,
Posted by Adam Bien on March 14, 2009 at 10:01 AM CET #
That is an excellent response, thank you. We're a paying GlassFish customer and wanted to buy a support incident from SpringSource when having some IoC container problems with JPA. They wouldn't sell us a support incident, they wanted to sell us 1 year support contract at a reduced price of $22,500!!! They may have changed the pricing now since I blogged about it and caused a lot of community reaction.
Posted by Ryan on March 15, 2009 at 11:54 PM CET #
Have you ever used JBoss Seam for one of your projects?
What are your experiences?
I've read two books on JBoss Seam and played a lot with the examples and it seems really awesome.
But I've not yet had the possibility to use it in a production environment.
Posted by Claus Hausberger on March 17, 2009 at 11:31 AM CET #