[jira] [Commented] (DOSGI-255) WsProvider does not get activated without OSGi HttpService

["Christian Schneider (JIRA)" <ji...@apache.org>]

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

Christian Schneider commented on DOSGI-255:
-------------------------------------------

Hmm .. this is an interesting problem. I think we have different issues here.
1. For the client we will never need a HTTPService
2. For the server it depends how the address looks like. If it contains the full uri then we do not need a HTTPService. 

I am not sure how to model this situation correctly. 
I would like to retain the fully async nature of DOSGi. Currently we have a good state where services only come up when all requirements are there. 

One possible improvement would be to redesign the aries rsa extension interface and split it up into a client and server side transport. This would allow the client to work completely without the HTTPService and still avoid actively waiting for a service.

For the server side we might be able to use intents for the HTTPService. We could somehow add the intent "HTTPService" to the service if we know it needs the HTTPService. We could then implement the HTTPServiceManager as an intent and only make it available when the HTTPService is present. 
I am not sure though if that would work out in practice.

For the mean time you can work around this by just creating a small dummy service with the HTTPService interface.

> 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 to get WsProvider running.
> 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)