[news.eclipse.technology.ejb-orm] Re: ejb3-orm currently not usable for

["Robert Greene" <rgreene@xxxxxxxxxxx>]

Hi Jorg,

 

The latest draft specification of JSR220 does define how it will work outside of a managed environment.  There is a bootstrap class called javax.persistence.Persistence that is used to get ahold of an EntityManagerFactory.  There are now 4 implementations in preview form that I am aware of available either commercially or through open source.

 

Regards,

-Robert

 

 

Right. To contribute a little to possible differentiation and competition, isn't it that EJB 3.0 currently does not specify execution outside a managed environment? I mean, they have it as a goal, but, as far as I know, as of today there does not exist any common specified API that is implemented by different vendors. At least ejb-3_0-dr2-spec-persistence.pdf has to say about

2.9 APIs for Obtaining and Using an EntityManager in non-J2EE Environments
[Note to readers] This area will be addressed in the next draft of this specification.

So, to note something differentiating that is important "for today", EJB 3.0 currently cannot be used on the client side, i.e. it currently cannot be used for applications based on the Eclipse Rich Client Platform, while JDO 2.0 (jsr220-orm) can. Given that this is not even specified yet in EJB 3.0, it will still take some time once it is until there will exist any reliable implementations.