cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Meinl (JIRA)" <>
Subject [jira] [Commented] (CXF-6347) CXF bundle activators not called in Eclipse/Equinox
Date Thu, 15 Oct 2015 15:54:05 GMT


Thorsten Meinl commented on CXF-6347:

As I said, not setting this header means that the activator is only called when you explicitly
start a bundle. Which basically never happens in Eclipse because everything is done lazily.
If Karaf honors Bundle-ActivationPolicy it should to no harm because the spec says:

... Currently, the only supported value for this is lazy, which means that once the bundle
is to be started, it does not invoke the Bundle-Activator's start() method until the first
access of a class is received.

But I guess you don't need the activator be called before you access a class in it (but for
this I'm not enough an export in CXF).

> CXF bundle activators not called in Eclipse/Equinox
> ---------------------------------------------------
>                 Key: CXF-6347
>                 URL:
>             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

View raw message