Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 95352 invoked from network); 11 Sep 2010 15:16:07 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Sep 2010 15:16:07 -0000 Received: (qmail 95454 invoked by uid 500); 11 Sep 2010 15:16:07 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 95328 invoked by uid 500); 11 Sep 2010 15:16:05 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 95320 invoked by uid 500); 11 Sep 2010 15:16:05 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 95317 invoked by uid 99); 11 Sep 2010 15:16:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Sep 2010 15:16:05 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Sep 2010 15:16:02 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o8BFFf7e027284 for ; Sat, 11 Sep 2010 15:15:41 GMT Message-ID: <8528036.14141284218141062.JavaMail.jira@thor> Date: Sat, 11 Sep 2010 11:15:41 -0400 (EDT) From: "Christopher Hunt (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Issue Comment Edited: (CAMEL-3117) cxfbean and cxfrs components should honour jax-rs providers in the bean registry In-Reply-To: <6287593.14031284182140366.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61774#action_61774 ] Christopher Hunt edited comment on CAMEL-3117 at 9/11/10 11:15 AM: ------------------------------------------------------------------- I've subsequently thought that it'd be easier (and consistent) for the component to have a list of providers specified; in a similar fashion to how handlers are specified for the jetty component. For example: .to("cxfbean:mybean?providers=#myprovider1,#myprovider2"); This also means that I'm constraining the provider specification in the manner above to the cxfbean component. This is because the cxfrs component already allows the specification of providers via the cxf:rsServer element. I'll attach the code required to make this happen for the cxfbean component now. was (Author: huntc@internode.on.net): I've subsequently thought that it'd be easier (and consistent) for the component to have a list of providers specified; in a similar fashion to how handlers are specified for the jetty component. For example: .to("cxfbean:mybean?providers=#myprovider1,#myprovider2"); I'll attach the code required to make this happen. > cxfbean and cxfrs components should honour jax-rs providers in the bean registry > -------------------------------------------------------------------------------- > > Key: CAMEL-3117 > URL: https://issues.apache.org/activemq/browse/CAMEL-3117 > Project: Apache Camel > Issue Type: Improvement > Components: camel-cxf > Affects Versions: 2.4.0 > Environment: cxfrs and cxfbean > Reporter: Christopher Hunt > > The cxfbean component does not presently provide a means of using custom providers i.e. those customised JAX-RS classes that are annotated with the @Provider declaration. > My recommendation is that objects instantiated in the bean container from classes annotated with @Provider are automatically registered for use by the cxfrs and cxfbean components. This includes message body writers/readers and parameter handlers i.e. anything that can be presently expressed in the cxf:rsServer/providers element. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.