Eclipse Community Forums: Gemini » Gemini JPA: single persistence bundle too restrictive

Home » Eclipse Projects » Gemini » Gemini JPA: single persistence bundle too restrictive(Constraint that all entities should be defined in a single persistence bundle is too restrictive)

Show: Today's Messages :: Show Polls :: Message Navigator

Gemini JPA: single persistence bundle too restrictive [message #1028016]

Wed, 27 March 2013 18:20

Jan Vermeulen

Messages: 11
Registered: September 2010

Junior Member

I have recently upgraded our OSGi-based business framework to EclipseLink 2.4.x from an older version, and I have come to the conclusion that Gemini is not an option, because it requires that all entities are defined in a single persistence bundle.

Our framework is built up of hundreds of entities spread over tens of separate bundles. That is required to make the code modular and reusable. I have been able to maintain that architecture with the older version of the OSGi support for JPA, including the use of dynamic weaving. But that does not seem to be possible with the current Gemini JPA solution.

Is there any chance that restriction is overcome in a future version ? And will that also include support for dynamic weaving, since the tricky part is precisely in providing the weaver with metadata that must come from annotations on the same classes it is loading ?

Report message to a moderator

Re: Gemini JPA: single persistence bundle too restrictive [message #1028215 is a reply to message #1028016]

Thu, 28 March 2013 01:08

Michael Keith

Messages: 243
Registered: July 2009

Senior Member

Hi Jan,

The earlier version of EclipseLink OSGi was coupled to Equinox and required some very specific Equinox hook support. It also required that EclipseLink be installed as a system extension bundle. Long story short, it was a proprietary point solution and less than ideal.

Gemini JPA provides an implementation of the OSGi JPA standard and will work on any compliant OSGi framework. Unfortunately, the OSGi JPA standard is not as flexible as it could/should have been and does not permit multiple bundles to contribute to the same persistence unit. There is a Gemini JPA enhancement request that is currently open, though, to support this:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=363195

Dynamic weaving might be difficult just because the bundles must not be loaded before the classes get weaved, and the process for finding all of the bundles makes it more likely that at least one of them could get started before it gets found by Gemini JPA. That would likely require a refresh. In any case, if you could please comment and/or respond to questions that I ask in that bug then it would help me as I develop that feature.

Thanks,
-Mike

Report message to a moderator

Previous Topic:	Gemini + e4 +Injection Dependency
Next Topic:	Mapping class from another plug-in

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 13:15:34 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter