Issue Details (XML | Word | Printable)

Key: NUCJPA-248
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Peter Kriens
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
DataNucleus API JPA

Datanucleus JPA depends on Blueprint unnecessary

Created: 03/Sep/13 06:11 PM   Updated: 18/Nov/13 03:31 PM
Component/s: None
Affects Version/s: 3.3.0.release
Fix Version/s: None

Severity: Development


 Description  « Hide
There is an unnecessary dependency in Datanucleus on Blueprint. Since it is trivial to to register a service in a BundleActivator, which does not introduce dependencies, it would be much nicer if the Blueprint dependency was removed.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 08/Oct/13 04:25 PM
Thanks, why not provide a sample BundleActivator for inclusion and then this can be done? Resource is very limited here and I don't have great experience with OSGi (nor much time to find out)

Peter Kriens added a comment - 08/Oct/13 04:55 PM
I agree, it seems a waste to use Blueprint to only register a single service. If you need help, do not hesitate to contact me.

Andy Jefferson added a comment - 08/Oct/13 05:31 PM
Hi Peter, I was suggesting that (if you have time) you could contribute a "BundleActivator" (attach to this issue). Any questions that need answers in order to do this just post them here and I'll try to get you a quick answer.

Anything issue specific to DataNucleus itself, requiring no knowledge of OSGi, (e.g NUCJPA-247 you raised) I'll look at when time permits.

Peter Kriens added a comment - 08/Oct/13 05:50 PM
Could we have a Skype chat so you can guide me through the sources? Otherwise I spent most of my time figuring out where/how to start ... I am pkriens on Skype

Andy Jefferson added a comment - 18/Nov/13 03:31 PM
I added a sample XXXActivator (org.datanucleus.api.jpa.OSGiActivator) some time ago (as advised by email). What I haven't done is add any associated MANIFEST to go with that to enable its use. Perhaps that is the way to go and you can adapt this, and contribute something complete that works in all OSGi envs? Thx