Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA36918537 for ; Thu, 31 Mar 2016 11:56:25 +0000 (UTC) Received: (qmail 21638 invoked by uid 500); 31 Mar 2016 11:56:25 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 21600 invoked by uid 500); 31 Mar 2016 11:56:25 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 21559 invoked by uid 99); 31 Mar 2016 11:56:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Mar 2016 11:56:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 86DA42C1F61 for ; Thu, 31 Mar 2016 11:56:25 +0000 (UTC) Date: Thu, 31 Mar 2016 11:56:25 +0000 (UTC) From: "Christian Schneider (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DOSGI-140) Support the registration of multiple bundles sharing the same HTTP context MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DOSGI-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated DOSGI-140: -------------------------------------- Fix Version/s: (was: 1.8.0) 1.9.0 > 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: DSW > Reporter: Sergey Beryozkin > Fix For: 1.9.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 (v6.3.4#6332)