EJB 3... why should I learn it?

[Stephane Clinckart]

Hi,

I worked with EJB 1 & EJB 2 some years ago.
For a while now I'm using Hibernate... and now more and more iBatis.

Why should I learn EJB3?
What are the benefits?

I had lot of performance problems with EJB before...
At the end, it cost me more efforts to solve the problems that writing the DAO layer by the hand.
--> I would like to be convinced before I learn EJB3.

Thanks for you oppinion and arguments.

Stephane

[Paul Sturrock]

If you have worked with EJB 1 and 2 you will be well aware that EJB != a persistance technology alone. Stateless session beans have always been useful and continue to be so.

[Stephane Clinckart]

Paul Sturrock wrote:If you have worked with EJB 1 and 2 you will be well aware that EJB != a persistance technology alone. Stateless session beans have always been useful and continue to be so.

Yes..; sorry... I was only speaking about the persistance layer in my message... but of course EJB are usefull for managing beans.

But since framework like Spring exist... and that the EJB persistance layer don't really add some real extra value (in my opinion) vs hibernate or iBatis.

where is the interest/benefit to learn (what is the average learning curve?)... and use EJB3?

That is why I ask: Why should I learn it?

Thanks for the response.

Stephane

[Paul Sturrock]

Not sure I completely follow. If you already know the SLSB part of EJB (which hasn't really changed a great deal) surely its a greater effort to learn Spring? (not that I'm saying Spring has no value or less value, just that your question is based on effort).

and that the EJB persistance layer don't really add some real extra value (in my opinion) vs hibernate or iBatis

Persistance in EJB3 is JPA which is a specification, not an implementation. One of the leading implementations is ... Hibernate. iBatis on the other hand is a completely different beast. Given JPA was written with the lessons learned from Hibernate in mind (and by some of the Hibernate team) if you already know Hibernate you probably know or will quickly recognise all the concepts of JPA.

[Stephane Clinckart]

Paul Sturrock wrote:Persistance in EJB3 is JPA which is a specification, not an implementation. One of the leading implementations is ... Hibernate. iBatis on the other hand is a completely different beast. Given JPA was written with the lessons learned from Hibernate in mind (and by some of the Hibernate team) if you already know Hibernate you probably know or will quickly recognise all the concepts of JPA.

Hi,

thanks... I didn't know that.

The learning curve looks smaller now...

Thanks again.

Kind regards,

Stephane