[
https://issues.apache.org/jira/browse/CXF-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967745#comment-14967745
]
Daniel Kulp commented on CXF-6347:
----------------------------------
I've been playing with this a bit today and while adding the header doesn't
seem to harm anything, it also doesn't solve all the problems in Equinox due to
what I explicitly mentioned above. If my "service bundle" which implements
the service uses pure JAX-WS or JAX-RS API's and just a blueprint XML file to
expose it, CXF won't start. Aries blueprint goes into a grace period waiting
for the appropriate namespace handler service to start. There is nothing in
the service bundle (other than the namespace) that references CXF so nothing
triggers the start. Once I start the cxf-rt-frontend-jaxws bundle, then the
service proceeds as that would trigger the Activator in that bundle which would
then register the namespace handler.
> 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)
