Eclipse Community Forums: Gemini » [Gemini JPA] The Start order of the Domain Bundle is important?

Home » Eclipse Projects » Gemini » [Gemini JPA] The Start order of the Domain Bundle is important?(Weird missing import's occour when bundle is not the first)

Show: Today's Messages :: Show Polls :: Message Navigator

[Gemini JPA] The Start order of the Domain Bundle is important? [message #850444]

Fri, 20 April 2012 03:28

Eduardo Frazão

Messages: 123
Registered: January 2012

Senior Member

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: Fri, 20 April 2012 03:29]

Report message to a moderator

Re: [Gemini JPA] The Start order of the Domain Bundle is important? [message #850651 is a reply to message #850444]

Fri, 20 April 2012 07:52

Michael Keith

Messages: 243
Registered: July 2009

Senior Member

I seem to recall someone having problems when refreshing a bundle in Virgo (which is exactly what Gemini JPA will do when the persistence unit bundle is already started before the Gemini JPA bundles). One way you can check is to turn off weaving and set the Gemini refresh option to not refresh and see if the problem goes away.

-Mike

Report message to a moderator

Re: [Gemini JPA] The Start order of the Domain Bundle is important? [message #850833 is a reply to message #850651]

Fri, 20 April 2012 11:21

Eduardo Frazão

Messages: 123
Registered: January 2012

Senior Member

Thanks Mike!
Gemini JPA is always the first Bundle here.
The domain bundle must the first of the "Application bundles", else, this strange missing imports problem occour.
It can be related to weaving process? Another bundle pick a export domain class before it is weaved?

Report message to a 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 16:18

Michael Keith

Messages: 243
Registered: July 2009

Senior Member

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

Report message to a moderator

Previous Topic:	Implementation of OSGi Enterprise Transaction Service
Next Topic:	Gemini Web 2.1.0.M03

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 16:25:16 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter