[
https://issues.apache.org/jira/browse/CMIS-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sascha Homeier updated CMIS-932:
--------------------------------
Summary: Consider removing lazy activation policy for OpenCMIS OSGI Client
Wrapper (was: Consider removing lazy bundle activation for OpenCMIS OSGI
Client Wrapper )
> Consider removing lazy activation policy for OpenCMIS OSGI Client Wrapper
> --------------------------------------------------------------------------
>
> Key: CMIS-932
> URL: https://issues.apache.org/jira/browse/CMIS-932
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-client
> Affects Versions: OpenCMIS 0.13.0
> Environment: OSGi
> Reporter: Sascha Homeier
> Priority: Minor
> Labels: osgi
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
