dev@glassfish.java.net

Re: fighterfish.osgi-jpa resolved failed

From: Tang Yong <tangyong_at_cn.fujitsu.com>
Date: Thu, 10 Jan 2013 18:51:56 +0900

OK, I will confirm my source and the issue again.

Thanks
--Tang

Sahoo wrote:
> There seems to be something wrong with your setup.
>
> I don't think eclipselink has been upgraded recently. The version in use
> is 2.5.0-M5. I have a build of GF from yesterday and the osgi-jpa module
> resolves fine in that build as shown below:
>
> ss141213_at_Sahoo:/space/ss141213/WS/ff/trunk/test/it$ asadmin osgi inspect
> p r 293
> org.glassfish.fighterfish.osgi-jpa [293] imports packages:
> ----------------------------------------------------------
> org.osgi.framework; version=1.6.0 -> org.apache.felix.framework [0]
> org.osgi.service.packageadmin; version=1.2.0 ->
> org.apache.felix.framework [0]
> org.osgi.util.tracker; version=1.5.0 -> org.apache.felix.framework [0]
> javax.xml.bind.annotation.adapters; version=2.2.7 -> jaxb-api [2]
> javax.xml.bind.annotation; version=2.2.7 -> jaxb-api [2]
> javax.xml.bind; version=2.2.7 -> jaxb-api [2]
> org.glassfish.internal.api; version=4.0.0 ->
> org.glassfish.main.common.internal-api [128]
> org.eclipse.persistence.tools.weaving.jpa; version=2.5.0 ->
> org.eclipse.persistence.jpa [175]
> com.sun.enterprise.util.io; version=4.0.0 ->
> org.glassfish.main.common.util [186]
> org.glassfish.api.deployment; version=4.0.0 ->
> org.glassfish.main.common.glassfish-api [202]
> org.glassfish.api.deployment.archive; version=4.0.0 ->
> org.glassfish.main.common.glassfish-api [202]
> com.sun.enterprise.deploy.shared; version=4.0.0 ->
> org.glassfish.main.deployment.common [265]
> org.glassfish.osgijavaeebase; version=1.0.5 ->
> org.glassfish.fighterfish.osgi-javaee-base [299]
>
>
> ss141213_at_Sahoo:/space/ss141213/WS/ff/trunk/test/it$ asadmin osgi headers 175
>
> EclipseLink JPA (175)
> ---------------------
> Archiver-Version = Plexus Archiver
> Build-Jdk = 1.6.0_21
> Built-By = hudsonbuild
> Bundle-ManifestVersion = 2
> Bundle-Name = EclipseLink JPA
> Bundle-RequiredExecutionEnvironment = JavaSE-1.6
> Bundle-SymbolicName = org.eclipse.persistence.jpa
> Bundle-Vendor = Eclipse.org - EclipseLink Project
> Bundle-Version = 2.5.0.v20121120-ec51fcc
> ...
>
> ss141213_at_Sahoo:/space/ss141213/WS/ff/trunk/test/it$ asadmin osgi headers 110
>
> EclipseLink ASM (110)
> ---------------------
> Bundle-ManifestVersion = 2
> Bundle-Name = EclipseLink ASM
> Bundle-RequiredExecutionEnvironment = J2SE-1.5
> Bundle-SymbolicName = org.eclipse.persistence.asm
> Bundle-Vendor = Eclipse.org - EclipseLink Project
> Bundle-Version = 3.3.1.v201206041142
>
> It seems to me that you are using a different version of eclipselink
> asm. Did you upgrade it by yourself or you have an older build?
>
> Yes, we have to ensure that fighterfish modules can function while
> upgrading bundles. We have continuous integration tests which run for
> every glassfish build to ensure osgi-javaee features work properly.
>
> Thanks,
> Sahoo
>
> On Thursday 10 January 2013 02:02 PM, Tang Yong wrote:
>> 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
>>>
>>>
>>>
>
>
>