You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Christopher Hunt (JIRA)" <ji...@apache.org> on 2010/09/11 17:13:40 UTC
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61774#action_61774 ]
Christopher Hunt commented on CAMEL-3117:
-----------------------------------------
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.