Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 43630 invoked from network); 3 Jun 2010 22:42:37 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Jun 2010 22:42:37 -0000 Received: (qmail 76382 invoked by uid 500); 3 Jun 2010 22:42:37 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 76333 invoked by uid 500); 3 Jun 2010 22:42:37 -0000 Mailing-List: contact dev-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 dev@cxf.apache.org Received: (qmail 76325 invoked by uid 99); 3 Jun 2010 22:42:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jun 2010 22:42:36 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sberyozkin@gmail.com designates 209.85.161.41 as permitted sender) Received: from [209.85.161.41] (HELO mail-fx0-f41.google.com) (209.85.161.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jun 2010 22:42:30 +0000 Received: by fxm14 with SMTP id 14so521824fxm.0 for ; Thu, 03 Jun 2010 15:42:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=jXc5nUpBmAbP/G0h20NrRXYzzXBF8cYH3sV/89zVo34=; b=dqvcm9pawVeuDCdIEforEcd6TjysAtq7i8im9GHPk/Oa2pw1hJb9VNW4Ejy+uNPvwL 6OiaCyHAKlAR6jrwtGXj/MVm8xcfPtnFHxGx/ZfZNdVAXa/jeVhqZ3He7kcTgYsU10sC O1lQ/a1ZnoZI0JeSrNWsUUuGZWrVG91gKD+6A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=nXfaSjE3eL9lIQrQsbxZELrmtd6QftGQHbqAqA1MUT5E4GFZydwm6Gzo2ognrfo3FZ 7dn3YimYMDKRAqUaGLAvm3rdouLtx7V3COH4Pc6WDbPM04oif2Vjk+I7oT+Yczis2lk4 CSZuuTUBV6h8sAU/nXlHnPACMH0RmHWWbjgRc= MIME-Version: 1.0 Received: by 10.239.140.197 with SMTP id y5mr29637hby.184.1275604929745; Thu, 03 Jun 2010 15:42:09 -0700 (PDT) Received: by 10.239.178.132 with HTTP; Thu, 3 Jun 2010 15:42:09 -0700 (PDT) In-Reply-To: References: Date: Thu, 3 Jun 2010 23:42:09 +0100 Message-ID: Subject: Re: CXF-DOSGi passing the OSGi Remote Services and Remote Service Admin CT From: Sergey Beryozkin To: dev@cxf.apache.org Content-Type: multipart/alternative; boundary=001485f6299ab61481048827ea31 X-Virus-Checked: Checked by ClamAV on apache.org --001485f6299ab61481048827ea31 Content-Type: text/plain; charset=ISO-8859-1 Hi David On Wed, Jun 2, 2010 at 10:17 PM, David Bosschaert < david.bosschaert@gmail.com> wrote: > >> > >> > > - consolidation of DOSGI RI specific properties. Example, you added a > useful > > property called "org.apache.cxf.ws.port" so JAXRS endpoints need to > 'catch > > up' with "org.apache.cxf.rs.port". > > Perhaps we can continue adding such 'parallel' properties, but I'm > > wondering, can "org.apache.cxf.ws.port" > > be replaced with "org.apache.cxf.endpoint.port" or > > "org.apache.cxf.http.port" ? Later on, in post 1.2, we can deprecates > some > > of other 'duplicate' properties. > > >> 3. Anything else? > Well, the Remote Services Admin spec mandates that the configuration > properties follow a certain pattern. If the configuration type is > called org.apache.cxf.ws then its specific configuration variables > should be called org.apache.cxf.ws.something (see table 122.1 in the > OSGi 4.2 Enterprise Spec http://www.osgi.org/Download/Release4V42). > This is to avoid name clashes when you want to expose a service using > multiple Remote Service implementations that may not be aware of each > other. So to be compliant we have to live with parallel properties. > > Having some properties in the CXF space "org.apache.cxf" seems to be totally compliant ? Then they can be 'inherited' by cxf.ws, cxf.rs. > I do agree on matching up the properties where this makes sense across > org.apache.cxf.ws and org.apache.cxf.rs > > So how would you rename a property like "org.apache.cxf.ws.port" ? > > - HTTPS support ? May be a discussion on the dev list can be initiated, > a > > solution agreed upon and then someone from the community can step forward > > and work on it ? As a side note, a CXF user has approached me regarding > > fixing a JAXRS Jettison issue in DOSGI 1.1 (default Jettison provider > does > > not work in DOSGi 1.1, needs to be fixed for 1.2 too) so I think there > are > > experienced and motivated users who can help... > > While I agree that this would be great to have, I'm not sure if we > should wait for it to be finished. I'm not aware of anyone working on > this at the moment (please correct me if I'm wrong!). Months of work > have gone in making CXF-DOSGi compliant with the spec and I don't > think we should hold releasing this off until a nice piece of > functionality which hasn't even been started on has been finished. > There's nothing wrong with releasing often, so if this functionality > appears we can do a release again, unless someone is already working > on HTTPS support of course... > > Sure, it's been a big effort indeed. Perhaps HTTPS can even be implemented 'out of band' by users if needed : http://wiki.ops4j.org/display/paxweb/SSL+Configuration; future DOSGI releases may support it at the intents level thanks, Sergey > Best regards, > > David > --001485f6299ab61481048827ea31--