cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Panu Hämäläinen (JIRA) <j...@apache.org>
Subject [jira] [Created] (DOSGI-255) WsProvider does not get activated without OSGi HttpService
Date Fri, 10 Feb 2017 05:57:41 GMT
Panu Hämäläinen created DOSGI-255:
-------------------------------------

             Summary: WsProvider does not get activated without OSGi HttpService
                 Key: DOSGI-255
                 URL: https://issues.apache.org/jira/browse/DOSGI-255
             Project: CXF Distributed OSGi
          Issue Type: Bug
    Affects Versions: 2.0.0
            Reporter: Panu Hämäläinen


I have a DOSGi client-only environment which only needs to import services, no exports. The
environment does not need OSGi HttpService for anything so it is not installed to the OSGi
framework. However, it turns out that  org.apache.cxf.dosgi.dsw.handlers.ws.WsProvider does
not get activated if HttpService is unavailable and thus no DOSGi service gets imported (actually
WsProvider requires HttpServiceManager which requires HttpService).

As I did not want to install a full HttpService (because it is not really needed), I just
implemented a stub HttpService which does nothing else but publishes itself to the OSGi registry.

Can this be somehow improved so that service imports would work without a HttpService?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message