[
https://issues.apache.org/jira/browse/CXF-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967532#comment-14967532
]
Thorsten Meinl commented on CXF-6347:
-------------------------------------
If you read design document for lazy activation it becomes clear that Equinox
behaves according to the standard: http://www.osgi.org/Design/LazyStart. It
clearly states that in case of lazy activation (which Equinox does for very
good reason that are also described in the linked document) the bundle is only
activated when Bundle-ActivationPolicy is set to lazy. From the comments above
it seems that most other OSGi frameworks don't support lazy activation and
bundles are always explicitly activated. In this case specifying this header
should not have any effect (somehow using something else than Equinox has to
confirm this, though).
The current state is simply that the CXF are unusable in Equinox. If you don't
want to support Equinox and/or lazy activation or if it breaks other frameworks
this would be unfortunate and you should clearly state it.
> CXF bundle activators not called in Eclipse/Equinox
> ---------------------------------------------------
>
> Key: CXF-6347
> URL: https://issues.apache.org/jira/browse/CXF-6347
> Project: CXF
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 3.0.4
> Environment: Eclipse 4.4
> Reporter: Thorsten Meinl
>
> The CXF bundles have OSGi activators that perform initialization stuff such
> as looking for CXF services in other bundles. However, in Equinox the bundle
> activators are not called unless one explicitly starts the bundles. The
> default strategy in Equinox is not to start bundles, unless the
> "Bundle-ActivationPolicy" is set to "lazy". Therefore this header should be
> added to all bundles so that CXF (esp. the client) is also usable inside an
> Eclipse application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
