[News.eclipse.technology.eclipselink] Re: Eclipselink status

[shaun.smith@xxxxxxxxxx (Shaun Smith)]

> I am curious of the status of the contribution?  

We're working to get the initial code contribution ready for an initial IP 
review so we can check it in.  The Eclipse Foundation will do a more 
thorough IP check while we continue to work on the code in the Eclipse 
subversion repository.

> I am working on some 
> bundles that are using JPA and I am having some difficulty trying them 
> out using toplink in an osgi environment.  My issues are mainly around 
> class loading.  As far as I can see there is no way for me to tell 
> toplink programmatically where the classes live.  I am using the 
> <exclude-unlisted-classes>false</exclude-unlisted-classes> setting.  But 
> when i do a find i receive. "Unknown entity bean class:"  The class is 
> definitely defined with @Entity.  I would imagine this is due to it not 
> being on the class path.  The bundle can't have a direct dependency to 
> toplink because we need to be able to drop in other bundles and it can't 
> be implementation specific it has to work with other JPA providers.

Stephan Eberle and I recently joined the Teneo project for building JPA 
support for EMF and Stephan packaged TopLink Essentials up as a plugin.  
We initially ran into the same class loader visibility problem which 
Stephan overcame by enabling buddy classloading in the TopLink Essentials 
plugin.  This let TLE see the Entities in dependent plugins/bundles.  
Perhaps this is what you need to do?

FYI, we'll be building JPA persistence support for EMF models with 
EclipseLink as soon as the EclipseLink code is available.

--Shaun