[news.eclipse.rt.eclipselink] Re: Equinox weaving configuration - Claslo

[Thomas Haskes <t.haskes@xxxxxxx>]

Shaun, Thanks for all the information, the situation is much clearer to
me no.
> This situation will be improving in future releases of EclipseLink.  We
> have a few initiatives on-going.  We're investigating a non-temploader
> approach to weaving, it may be possibile to leverage the work of the
> Equinox Aspects team to implement EclipseLink's weaving in OSGi, and the
> OSGi JPA RFC 143 will introduce standards around how JPA should work in
> OSGi.  So there is quite a lot going on in this area but it is still in
> process.

I hope so, and will be following what comes up in future releases. It
seems to me that the JPA standard is not really aware of the modularity
the OSGi Envrionment enables, and it is well known that the classloading
algorithms are the most complicated part when it comes to deploy
osgi-fied versions of java libraries.

> Until then, I'm afraid if you want to use dynamic weaving you'll have to
> live with the current restrictions.  Your other alternative is to use
> static weaving.

While our product is designed to be modular, I can't have all the
entities in one bundle right now (we are not happy about having the
persistence.xml with the list of ALL entities in just one bundle that
has to be adjusted every time a new bundle with new enitities is
deployed, but since it is possible to do that without recompiling and
deploing, we can live with that restriction).
I'll stick with static weaving then. Although it complicates the
doployment process a little bit, this seems to be the best workaround
for my situation right now - thanks for the hint. Btw I must say that
besides those limitations about weaving the Eclipselink OSGi Bundles
work really good - great work.

Tom