cxf-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/CXF-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959043#comment-14959043
] 

Thorsten Meinl commented on CXF-6347:
-------------------------------------

Equinox does not start bundles/call the activator when classes are loaded and "Bundle-ActivationPolicy:
lazy" is not set. You need to explicitly (i.e. programmatically) start a bundle in this case.
Setting "Bundle-ActivationPolicy: lazy" means that the bundle activator will be called before
the first class is loaded and this is what we want.
Not sure if this is standard or correct but this is how it works in Equinox.

> 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)

Mime
View raw message