Dear Pro
EJB 3.0 Authors,
This might be a good opportunity for me to ask a question which is rather important for me now.
I currently work for a software company building a solution on the basis of EJB 2.1. Well, Message Driven Beans are used most often, Session Driven Beans - sometimes, and for persistence we use Hibernate, with everything being deployed on
JBoss 4.
What I am thinking about now is when should I start learning EJB 3. The intent of the company is to start using EJB 3 at some point in the future, but that point might be quite far at the moment. There are always a number of things to learn, so if it is not of urgent importance, I would prefer to learn something else right now, not EJB 3.
Perhaps the most crucial factor here is the set of benefits which EJB 3 brings with it. From what I have read about this new version so far, it significantly simplifies development proccess. Enterprise Beans are not required now to extend or implement anything, they can be POJOs. No Home Interfaces are required. Annotations replace XML deployment descriptors...
But let's take my case. We have already got a number of Enterprise Beans 2.1 ready and working. And frankly speaking, I do not find the development and deployment of EJB 2.1 that difficult.
So here is the question:
Should I make learning EJB 3.0 in my specific situation a Priority Number One? Does the new version bring anything good, except of relative easiness of development and deployment?
Thank you,
Alexander