Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 98454 invoked from network); 12 Jun 2009 14:00:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jun 2009 14:00:29 -0000 Received: (qmail 4069 invoked by uid 500); 12 Jun 2009 14:00:40 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 3996 invoked by uid 500); 12 Jun 2009 14:00:40 -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 3986 invoked by uid 99); 12 Jun 2009 14:00:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jun 2009 14:00:40 +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: domain of jmholtzman@gmail.com designates 209.85.200.175 as permitted sender) Received: from [209.85.200.175] (HELO wf-out-1314.google.com) (209.85.200.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jun 2009 14:00:32 +0000 Received: by wf-out-1314.google.com with SMTP id 29so791990wff.30 for ; Fri, 12 Jun 2009 07:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=14KeLMq0fvmTXRPcGd3DTrIdJJxI2st809Pad8gSKNE=; b=qaBd17rC75Keh2ot0pwS9Dsv4VvMi2rBEXl/y3CX7asyJC+d4XMW+gWd3FiGIqMIIR zePP4jHvo9BrC2IXNPhRTohv5EVxjHDGdSgrFIncYKz9idd4ZsEF4wx7smf8wfz7JqzI 9uTEeuKNDpVHIn420simq8q1CiuZQLufRBbUI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=FDiWTRpQ9FiS1M2cJwSOAJVDH3QAw6H4lUXvm1eKtL8c+X7rbqvlNjhlRYaezuGo7F p3DqsbGBe9d6cxen2UWgbb/IgOHoxAkT76zjCoHIt9BrZUxQF+6E8zmQrrlCcGe25sqB wqztZi66hjPfG9YjpLmJDb0VzMMJPIH137UUY= MIME-Version: 1.0 Sender: jmholtzman@gmail.com Received: by 10.142.246.19 with SMTP id t19mr1476012wfh.146.1244815211898; Fri, 12 Jun 2009 07:00:11 -0700 (PDT) Date: Fri, 12 Jun 2009 07:00:11 -0700 X-Google-Sender-Auth: 25f9fc84699a1edc Message-ID: Subject: Whiteboard pattern for JAX-RS services From: Josh Holtzman To: dev@cxf.apache.org Content-Type: multipart/alternative; boundary=000e0cd2e6e68427f6046c2720f3 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd2e6e68427f6046c2720f3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I've got some code that allows OSGI bundles to use the whiteboard pattern to register restful services. When a service is registered with a specific property, say, "jaxrs.resource=true" the JAX-RS implementation registers that service as a JAX-RS resource. The same could be done with message body readers and writers, too. In my implementation, the JAX-RS servlet is registered under the "/rest/*" URL, and all of the JAX-RS resources fall below that, so /rest/foo can be provided by one bundle and /rest/bar could be provided by another. Is this something the CXF folks would be interested in adding? If so, does it belong in the cxf-minimal bundle, or as its own add-on bundle? If people are familiar with pax-web and pax-web-extender-whiteboard, they'll recognize that this kind of thing can be broken out into its own bundle. In the pax-web case, though, they decided to merge the whiteboard functionality into their main bundle. Full disclosure: I've been using another JAX-RS impl to do this, but with the CXF impl passing the 1.0 TCK, I figured that it's time to re-evaluate :) Thanks, Josh --000e0cd2e6e68427f6046c2720f3--