Description
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,
"org.apache.cxf.rs.httpservice.context=/rs" "org.apache.cxf.rs.address="/service"
will lead to "/rs/service" relative base address be created for a given endpoint.
It should be possible to do
// 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"
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:
// First bundle "org.apache.cxf.ws.address="/service1" // Second bundle "org.apache.cxf.ws.address="/service2"
means that both bundles have to be bound to the default CXF "/cxf" or "/services" context
Attachments
Issue Links
- is related to
-
DOSGI-126 Allow to use the servlet transport with automatic discovery
- Closed