I am new to EJB3 world. After going through different reviews and as i am coming from Hibernate world,
i would like to know is EJB3 worth to learn? In our company for the persistence layer, may be EJB3 will be
opted but what i was looking forward to know. As far as learning is concerned is it worth to learn EJB3 when
technologies like Hibernate and all are out? What are the prospects of learning EJB3 with respect to the job
market? I know it's kind of a dumb question, but as opinions are mixed, i would like to know opinions of fellows
who are already working in this technology.
EJB is about more than persistence. I would advise to start by learning about the persistence features, though - the JPA API. That also works in contexts that are not full JEE servers (like desktop applications and servlet containers), and is definitely a useful thing to know.
EJB also covers other architectural options - like sessions beans and message-driven beans. Those might be useful, too, but require a full JEE server (like GlassFish, WebLogic or WebSphere), so they're not used as widely.
I am working on EJB 3.0 with JPA Persistence..
I want to tell you one thing that 1 JPA itself is just a specification, not a product, it cannot perform persistence or anything else by itself. JPA is just a set of interfaces and requires an implementation (a persistence provider). There are open source and commercial JPA implementations (Toplink Essentials, EclipseLink, Hibernate EntityManager, OpenJPA, Kodo, etc) and any Java EE 5 (or Java EE 6) application server must provide support for its use (JBoss uses Hibernate EntityManager).
so here is too hibernate plays its role behind the scenes..
ANd EJB are flexible and portable and call be called remotely..Its good technolgy to work on..
I hope it will help you..
Thanks and Regards ..
A small leak can sink a Gigantic ship.>
Joined: Oct 28, 2010
Thanks for your valuable input.
I have worked over JPA and hibernate a little and as the new demand was arising i was thinking to put my hands on EJB3 as well.