|Re: EclipseLink weaving fragment require-bundle version [message #783710 is a reply to message #783483]
||Thu, 26 January 2012 09:26
| Charlie Mordant
Registered: July 2010
After reading the doc (one time again), I have some questions:|
My persistence.xml, my model classes and my EntityManager are defined in 3 different bundles (persistence.xml is a fragment of the entitymanager module).
Wich module must have the "Require-Bundle: org.eclipse.persistence.jpa;bundle-version="1.1.2"" Manifest entry?
Does the eclipselink start order must absolutely be
What if my hello bundle starts before the jpa.equinox one (or asm before antlr...), I have no control on my bundle start order but start level (running with Maven/Pax)?
Is the org.eclipse.update.configurator mandatory?
I did all of this without configurator, but my weaving fragment is not resolved (I'll try tonight with it).
My project also contains dependencies with equinox aspects, equinox hook and spring-weaving adaptor, can it be the source of the problem?
May I add the weaving fragment to the boot classpath (http://team.ops4j.org/wiki/display/paxrunner/Manage+boot+classpath#Managebootclasspath-bcp), bootdelegation or osgi-extra-package (there is an issue with pax and framework extension wich force this: https://github.com/nilshartmann/aries-spy-fly/blob/master/spi-fly-itests-old/src/test/java/org/apache/aries/spifly/CustomizerWithAopTest.java)?
Best regards, Charlie
Powered by FUDForum
. Page generated in 0.11391 seconds