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 14:09:05 GMT

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

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

As I said the bundle is *not* started by Equinox, therefore the activator is not called (which
is OK). You need the additional bundle header to force a start.
I don't want to use Karaf or anything else. It would work perfectly without any additional
stuff if this header was added. Currently this is a blocker for all Eclipse-based applications.

> 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