EclipseLink with Apache Felix

[Andreas Kollegger-2]

Hi all,

Back in July there was some discussion about a problem running  
EclipseLink with Apache Felix, ultimately sticking at a  
ClassNotFoundException:

java.lang.NoClassDefFoundError: javax/xml/namespace/QName
        at org.eclipse.persistence.internal.helper.ClassConstants.<clinit>
(ClassConstants.java:127)
        at  
org.eclipse.persistence.internal.identitymaps.AbstractIdentityMap.getDefaultIdentityMapClass
(AbstractIdentityMap.java:297)
        at org.eclipse.persistence.sessions.Project.<init>(Project.java:84)

There was mention of starting to use bnd in the build process (which  
was very encouraging) and looking for workarounds in the meantime.  
It's not that the system isn't exposing the javax.xml.namespace, but  
that the bundles aren't importing it.

As a test, I repackaged the comics example as a maven multi-module  
project which uses pax-runner to launch the bundle into plain-old-
felix. Any of the 1.1X and 2.0x bundles I've tried from the maven  
repositories still have the problem. The project is attached for  
reference. You can change the eclipselink version being deployed by  
just editing a property in the top-level pom.

Best,
Andreas



_______________________________________________
eclipselink-users mailing list
eclipselink-users@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

[tware]

Hi Andreas,

   The use of BND to generate our manifests on our trunk(2.0) stream is just
days away.  The targets are actually already available for those doing their own
build.  We just have a little work left to get them enabled on our build server.

-Tom

Andreas Kollegger wrote:

> Hi all,
>
> Back in July there was some discussion about a problem running
> EclipseLink with Apache Felix, ultimately sticking at a
> ClassNotFoundException:
>
> java.lang.NoClassDefFoundError: javax/xml/namespace/QName
>     at
> org.eclipse.persistence.internal.helper.ClassConstants.<clinit>(ClassConstants.java:127)
>
>     at
> org.eclipse.persistence.internal.identitymaps.AbstractIdentityMap.getDefaultIdentityMapClass(AbstractIdentityMap.java:297)
>
>     at org.eclipse.persistence.sessions.Project.<init>(Project.java:84)
>
> There was mention of starting to use bnd in the build process (which was
> very encouraging) and looking for workarounds in the meantime. It's not
> that the system isn't exposing the javax.xml.namespace, but that the
> bundles aren't importing it.
>
> As a test, I repackaged the comics example as a maven multi-module
> project which uses pax-runner to launch the bundle into plain-old-felix.
> Any of the 1.1X and 2.0x bundles I've tried from the maven repositories
> still have the problem. The project is attached for reference. You can
> change the eclipselink version being deployed by just editing a property
> in the top-level pom.
>
> Best,
> Andreas
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@...
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users

_______________________________________________
eclipselink-users mailing list
eclipselink-users@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

[Andreas Kollegger-2]

So, is bnd still not being used in the build process? I just tried the  
latest snapshots of 2.x and the released 1.1.3
build. The manifest is still wrong, missing a reference to  
java.xml.namespace which causes the ClassConstants class
to fail loading under Felix and even Equinox.

Should I raise a jira issue for it?

-Andreas

On Sep 14, 2009, at 10:53 PM, Andreas Kollegger wrote:

> Hi all,
>
> Back in July there was some discussion about a problem running  
> EclipseLink with Apache Felix, ultimately sticking at a  
> ClassNotFoundException:
>
> java.lang.NoClassDefFoundError: javax/xml/namespace/QName
> at org.eclipse.persistence.internal.helper.ClassConstants.<clinit>
> (ClassConstants.java:127)
> at  
> org.eclipse.persistence.internal.identitymaps.AbstractIdentityMap.getDefaultIdentityMapClass
> (AbstractIdentityMap.java:297)
> at org.eclipse.persistence.sessions.Project.<init>(Project.java:84)
>
> There was mention of starting to use bnd in the build process (which  
> was very encouraging) and looking for workarounds in the meantime.  
> It's not that the system isn't exposing the javax.xml.namespace, but  
> that the bundles aren't importing it.
>
> As a test, I repackaged the comics example as a maven multi-module  
> project which uses pax-runner to launch the bundle into plain-old-
> felix. Any of the 1.1X and 2.0x bundles I've tried from the maven  
> repositories still have the problem. The project is attached for  
> reference. You can change the eclipselink version being deployed by  
> just editing a property in the top-level pom.
>
> Best,
> Andreas
>
> <comics-osgi.zip>

_______________________________________________
eclipselink-users mailing list
eclipselink-users@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

[tware]

BND was recently integrated into the build process in 1.2 and 2.0.   (This
enhancement is currently not planned for 1.1.3) How recent is the 2.0 version
you are using?  Which bundle do you see the issue on?

-Tom

Andreas Kollegger wrote:

> So, is bnd still not being used in the build process? I just tried the
> latest snapshots of 2.x and the released 1.1.3
> build. The manifest is still wrong, missing a reference to
> java.xml.namespace which causes the ClassConstants class
> to fail loading under Felix and even Equinox.
>
> Should I raise a jira issue for it?
>
> -Andreas
>
> On Sep 14, 2009, at 10:53 PM, Andreas Kollegger wrote:
>
>> Hi all,
>>
>> Back in July there was some discussion about a problem running
>> EclipseLink with Apache Felix, ultimately sticking at a
>> ClassNotFoundException:
>>
>> java.lang.NoClassDefFoundError: javax/xml/namespace/QName
>>     at
>> org.eclipse.persistence.internal.helper.ClassConstants.<clinit>(ClassConstants.java:127)
>>
>>     at
>> org.eclipse.persistence.internal.identitymaps.AbstractIdentityMap.getDefaultIdentityMapClass(AbstractIdentityMap.java:297)
>>
>>     at org.eclipse.persistence.sessions.Project.<init>(Project.java:84)
>>
>> There was mention of starting to use bnd in the build process (which
>> was very encouraging) and looking for workarounds in the meantime.
>> It's not that the system isn't exposing the javax.xml.namespace, but
>> that the bundles aren't importing it.
>>
>> As a test, I repackaged the comics example as a maven multi-module
>> project which uses pax-runner to launch the bundle into
>> plain-old-felix. Any of the 1.1X and 2.0x bundles I've tried from the
>> maven repositories still have the problem. The project is attached for
>> reference. You can change the eclipselink version being deployed by
>> just editing a property in the top-level pom.
>>
>> Best,
>> Andreas
>>
>> <comics-osgi.zip>
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@...
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users

_______________________________________________
eclipselink-users mailing list
eclipselink-users@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-users