Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 44152 invoked from network); 5 Jun 2009 22:11:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Jun 2009 22:11:18 -0000 Received: (qmail 16142 invoked by uid 500); 5 Jun 2009 21:47:14 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 16114 invoked by uid 500); 5 Jun 2009 21:47:14 -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 16104 invoked by uid 99); 5 Jun 2009 21:47:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jun 2009 21:47:14 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.77.186.17] (HELO mx3.progress.com) (192.77.186.17) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jun 2009 21:47:05 +0000 Received: from mx3.progress.com (127.0.0.1) by mx3.progress.com (MlfMTA v3.2r9) id h5695i0171sn for ; Fri, 5 Jun 2009 17:46:44 -0400 (envelope-from ) Received: from progress.com ([192.233.92.16]) by mx3.progress.com (SonicWALL 6.2.2.1073) with ESMTP; Fri, 05 Jun 2009 17:46:42 -0400 Received: from NTEXFE02.bedford.progress.com (ntexfe02 [10.128.10.26]) by progress.com (8.13.8/8.13.8) with ESMTP id n55Lkgjk010117; Fri, 5 Jun 2009 17:46:42 -0400 (EDT) Received: from MAIL02.bedford.progress.com ([172.16.2.55]) by NTEXFE02.bedford.progress.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 5 Jun 2009 17:46:42 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9E627.1CE0D81E" Subject: Integrating JAX-RS runtime into DOSGi Date: Fri, 5 Jun 2009 17:46:52 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Integrating JAX-RS runtime into DOSGi Thread-Index: AcnmJyMqabmEval5QB6hTnkhDMQ8SQ== From: "Sergey Beryozkin" To: Cc: X-OriginalArrivalTime: 05 Jun 2009 21:46:42.0788 (UTC) FILETIME=[1D628A40:01C9E627] X-Mlf-Version: 6.2.2.1073 X-Mlf-UniqueId: o200906052146420249782 X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C9E627.1CE0D81E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi =20 I'm planning to integrate the JAX-RS runtime into DOSGi. Both JAXRS endpoints and client proxies can be created either from Spring or programmatically and they can work with JAXB, Aegis, XmlBeans. =20 First CXF minimal bundle needs to be updated to include cxf-frontend-jaxrs and depend on jaxrs-1.0 api. This should affect the overall bundle size too much.=20 =20 Next, as far as DOSGi RI is concerned : If HTTP intent is available and org.apache.cxf.dosgi.frontend.jaxrs is there then JAXRS gets involved, either on the server or the client sides. =20 I think that should be enough for a start. =20 Next we can ensure that no JAX-RS annotations are required for JAXRS runtime to operate in DOSGi case as we now support provisioning of the metadata out of band but it can be done later on.. =20 Josh, if you're interested then we can work on integrating JAX-RS into DOSGi together, given that you've provided a JAXWS patch.. =20 Cheers, Sergey ------_=_NextPart_001_01C9E627.1CE0D81E--