Panu Hämäläinen commented on DOSGI-225:

Ok, need to try. Probably the referred documentation should be updated then.

The bug seems to be related to DOSGI-159. If I want to expose my service at 
 I need to specify
- org.apache.cxf.ws.address=/myaddress (in my service properties)
- http://<org.ops4j.pax.web.listening.addresses>:<org.osgi.service.http.port> 
(in HttpServiceManager config with PID org.apache.cxf.dosgi.http)

Correct? What's the purpose of org.apache.cxf.ws.httpservice.context service 

> Service publication with org.apache.cxf.ws.httpservice.context property does 
> not work
> -------------------------------------------------------------------------------------
>                 Key: DOSGI-225
>                 URL: https://issues.apache.org/jira/browse/DOSGI-225
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>          Components: DSW
>    Affects Versions: 1.7.0
>            Reporter: Panu Hämäläinen
>            Assignee: Christian Schneider
>             Fix For: 2.0.0
> For org.apache.cxf.ws.httpservice.context the page 
> https://cxf.apache.org/distributed-osgi-reference.html says "When this 
> property is specified, the OSGi HTTP Service is used to expose the service, 
> rather than a dedicated Jetty HTTP Server. This property doesn't allow the 
> specification of a port number, as this is provided by the HTTP Service." 
> However, this does not work with DOSGi 1.7.0. Instead, the service gets 
> exposed (by PojoConfigurationTypeHandler) at the default address 
> http://localhost:9000. This used to work e.g. with 1.4.0.

This message was sent by Atlassian JIRA

Reply via email to