[CMIS-932] Consider removing lazy activation policy for OpenCMIS OSGI Client Wrapper

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: OpenCMIS 0.13.0
• Fix Version/s: OpenCMIS 0.14.0
• Component/s: opencmis-client
• Labels: osgi

Environment

OSGi

• Assignee: Florian Müller
• Reporter: Sascha Homeier
• Created: 06/Aug/15 08:15
• Updated: 12/Aug/15 16:08
• Resolved: 12/Aug/15 16:08

Description

Currently the bundle activation policy is set to 'lazy' for OpenCMIS OSGi Client library.
But inside the Bundle Activator a Service (SessionFactory) is registered programmatically (not via DS/SCR).
This leads to problems if for example bundle A binds the SessionFactory service via DS. Bundle A only gets activated when Client bundle is activated.

In my case I have problems in my integration tests for Bundle A where no classes from Client Bundle are called before receiving service from Bundle A (which again needs SessionFactory service).

Could you consider removing 'Bundle-ActivationPolicy: lazy' from manifest?

Just for reference:
http://wiki.osgi.org/wiki/Bundle-ActivationPolicy