[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.ejb-orm] correction: EJB3 is specified for use outside of a J2EE container
Max Rydahl Andersen schrieb:
vendors. At least ejb-3_0-dr2-spec-persistence.pdf has to say about

Please read the public draft and not the out-dated dr2.
Alright, I'm really sorry for this misinformation. Googling for "jsr220" brought up the EDR page on jcp.org, and I assumed there exists only a single page per JSR on jcp.org. I should have looked further. So EJB3 does specify persistence outside of a J2EE container, since one month.
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.

This is not true, and please note that JSR220 is called EJB3, not JDO.
Right, though that's not what I meant. I was referring to the Eclipse project jsr220-orm, which also produces JDO2 artifacts.

There exists at least two implementations of this and more to come.
Could you tell what these implementations are?
So, in short: EJB3 can be used on the client side today.
Given that the relevant part of the spec is only 1 month old, I doubt it a bit that "today" here really is today as in 8/2/2005...

Do you know of any RCP application, or some other client application with a GUI, that makes use of it? For JDO 2.0, I know at least of one in production use. We created that one using JPOX, though, not VOA.

By the way, there exists a new open source mapping tool and runtime to persist EMF models using JDO 2.0 (JPOX also): Elver. Mapping an EMF model to an RDBMS is really nice to have when creating RCP applications. I haven't tried Elver though, but only our own brew for doing the same.