[Gemini JPA] The Start order of the Domain Bundle is important? [message #850444] |
Thu, 19 April 2012 23:28  |
Eclipse User |
|
|
|
Hi all. Im using Gemini JPA with Virgo, and if my Domain Bundle is not the first, some Eclipselink class not found exceptions occour when createEntityManagerFactory of EntityManagerFactoryBuilder service is invoked.
Example:
Caused by: org.eclipse.virgo.kernel.osgi.framework.ExtendedClassNotFoundException: org.eclipse.persistence.internal.weaving.PersistenceWeaved in KernelBundleClassLoader: [bundle=br.com.centrocate.weld.domain_1.0.0]
(Importing this class causes other eclipselink classes missing, etc). If I change the deploy order, and put the domain bundle as first, no problem occours, and I dont need to import anything from eclipselink.
Thanks
Eduardo Frazão
[Updated on: Thu, 19 April 2012 23:29] by Moderator
|
|
|
|
|
Re: [Gemini JPA] The Start order of the Domain Bundle is important? [message #852054 is a reply to message #850833] |
Sat, 21 April 2012 12:18  |
Eclipse User |
|
|
|
Gemini JPA will actually refresh the bundle if is is already resolved, so if you keep restarting already-resolved bundles then you might get refreshing as well. I would set the option and see if it works around the refreshing problem. I am going to talk to the Virgo folks next week. I'll see if we can get a better understanding of the integration issues.
-Mike
|
|
|
Powered by
FUDForum. Page generated in 0.07196 seconds