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

Amichai Rothman commented on DOSGI-140:
---------------------------------------

Still waiting for this to work properly... and there's also DOSGI-197 and 
DOSGI-252.. multiple issues related to context/address configuration.

I think all combinations of context/address settings should be considered, 
including same/different context, same/different address, same/different 
bundles, with/without the root context and/or default context too. The proper 
desired behavior of each combination should be defined and fixed. Currently the 
only thing that works for me is using unique address and unique context per 
bundle, which makes for some badly named urls, and even then iirc there is some 
mixup (both addresses are available on both contexts - though it's possible 
this happened with some other combination of context/address settings).

Any chance this will get fixed once and for all?


> Support the registration of multiple bundles sharing the same HTTP context
> --------------------------------------------------------------------------
>
>                 Key: DOSGI-140
>                 URL: https://issues.apache.org/jira/browse/DOSGI-140
>             Project: CXF Distributed OSGi
>          Issue Type: Improvement
>          Components: common
>            Reporter: Sergey Beryozkin
>            Priority: Major
>             Fix For: 2.4.0
>
>
> When an application consists of different implementation bundles, it is not 
> possible at the moment to share the same HTTP context which makes it 
> difficult to rely on Servlet container support for sessions, security, etc.
> Note that right now it is possible for a bundle to use a combination of 
> HttpContext and relative ws/rs addresses, example,
> {code}
> "org.apache.cxf.rs.httpservice.context=/rs" 
> "org.apache.cxf.rs.address="/service"
> {code}
> will lead to "/rs/service" relative base address be created for a given 
> endpoint.
> It should be possible to do
> {code}
> // First bundle
> "org.apache.cxf.rs.httpservice.context=/rs" 
> "org.apache.cxf.rs.address="/service1"
> // Second bundle
> "org.apache.cxf.rs.httpservice.context=/rs" 
> "org.apache.cxf.rs.address="/service2"
> {code}
>  
> with both bundles binding to "/service" HTTP context but having different 
> base addresses ("/rs/service1", "/rs/service2"). 
> Perhaps we can also optimize when only relative ws/rs address property is 
> set, example:
> {code}
> // First bundle
> "org.apache.cxf.ws.address="/service1"
> // Second bundle
> "org.apache.cxf.ws.address="/service2"
> {code}
>  
> means that both bundles have to be bound to the default CXF "/cxf" or 
> "/services" context



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to