|Re: Classloading issue w/ TempEquinoxEntityLoader [message #495147 is a reply to message #494500]
||Tue, 03 November 2009 17:13
| Shaun Smith
Registered: July 2009
Just to confirm that in pre 2.0 EclipseLink you do need all of your entities in the same bundle as your persistence.xml for weaving to work. However as you have discovered this restriction will be gone in EclipseLink 2.0. This is because we've removed the need for direct access to the classloader of the persistence unit. So with EclipseLink 2.0 you can just create an EntityManagerFactory with the name of the persistence unit and no longer pass a classloader.
I'll be updating the OSGi examples on the wiki for EclipseLink 2.0.
Also, at Eclipse Summit Europe last week I was speaking with Martin Lippert who suggested that the way to enable weaving in an RCP app was to ensure that the org.eclipse.core.runtime bundle is started after the o.e.p.jpa and javax.persistence bundles. The core runtime bundle launches the RCP application and you want to make sure that EclipseLink has setup weaving before the application loads an Entity class. I haven't tried this out yet but thought I'd pass this on to you since you're actively working with RCP.
Powered by FUDForum
. Page generated in 0.08307 seconds