This makes me think a problem:
Although fighterfish aims to glassfish osgi-javaee, while updating
eclipselink(from the third part vendors) related bundles, we need to
take care of some changes from related bundles(especially some exported
packages) because fighterfish related modules maybe are using some
features from eclipselink.
Thanks
--Tang
Tang Yong wrote:
> Hi sahoo, team
>
> Using a snapshot based current glassfish trunk, after starting domain,
> in server.log, the following exception happened,
>
> [#|2013-01-10T17:03:22.906+0900|SEVERE|glassfish
> 4.0|javax.enterprise.logging.stderr|_ThreadID=12;_ThreadName=FelixStartLevel;_TimeMillis=1357805002906;_LevelValue=1000;|org.osgi.framework.BundleException:
> Unresolved constraint in bundle org.glassfish.fighterfish.osgi-jpa
> [297]: Unable to resolve 297.0: missing requirement [297.0]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.eclipse.persistence.tools.weaving.jpa)(version>=2.2.0))
> [caused by: Unable to resolve 216.0: missing requirement [216.0]
> osgi.wiring.package;
> (osgi.wiring.package=org.eclipse.persistence.internal.libraries.asm)]
> at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)
> at java.lang.Thread.run(Thread.java:722)
> |#]
>
> By analysing, originally, org.eclipse.persistence.internal.libraries.asm
> should be exported by org.eclipse.persistence.asm.jar, however, as to
> current version 2.5.0.v20121128-2ece041, package
> org.eclipse.persistence.internal.libraries.asm has been missed in
> org.eclipse.persistence.asm.jar.
>
> Thanks
> --Tang
>
>
>