[news.eclipse.technology.ejb-orm] Re: correction: EJB3 is specified for

["Max Rydahl Andersen" <max.andersen@xxxxxxxxx>]

> There exists at least two implementations of this and more to come.
> Could you tell what these implementations are?

The two I know is JBoss/Hibernate EntityManager  
(entitymanager.hibernate.org) and Oracle  
(http://www.oracle.com/technology/ejb3/index.html).
Others here can probably list more (I saw Robert mention 2 more)

> 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...

Well, I'm running it here ;)

> 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.

No, I don't know of any RCP application using EJB3 nor JDO2 (before the  
one you just mentioned).
But I know of a couple that uses Hibernate with Eclipse RCP and they  
should have
no apparent problems using it (but that of course is not what you asked  
for ;)

> 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.

Nice. I did not know JDO2 defined ways to persist arbitrary collections  
(EMF collections) efficiently,
are you sure that is not "just" JPOX features they are utilizing ?

EMF has some very intrusive design issues that makes it very hard to  
persist and query completely and efficiently -
would be interested in hearing how much they have solved of that.

/max