[news.eclipse.rt.eclipselink] Equinox weaving configuration - Clasloadin

[Thomas Haskes <t.haskes@xxxxxxx>]

Hi Guys,

I recently migrated an application from an JavaEE App server to an OSGi
Environment and was wondering why my application suddenly showed such a
poor performance, when I discovered that lazy loading of entities
doesn't work anymore because the entites are not woven.

A Google search on the topic brought me to this tutorial [1] which I
followed, but now I get ClassNotFoundExceptions.

I have the following setup on the server:

Bundle A contains all the entities and exports them, so that the client
can use the same bundle.

Bundle A.internal creates the EMF and the EM an does all the persistence
operations.

Now when I start my application, I get a ClassNotFoundException on my
entity classes, but only when I start the fragments
org.eclipse.persistence.equinox and org.eclipse.equinox.weaving (which
are required to start to get lazy loading working as mentioned in [1]).

If I dont start those fragments, everything works, but then theres no
weaving at all(which is clear as the fragment are not started). It seems
that I have to configure some more Bundle-Requirements or
Buddy-Classloading directives, but I don't know where and what.

I provided the EMF with the Classloader of the Activator of the Bundle
A.internal, and that works when I do not start the fragments.

Any Ideas?

TIA

Tom

[1]
http://wiki.eclipse.org/EclipseLink/Examples/OSGi/Equinox_Byte_Code_Weaving