camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Hunt (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-3117) cxfbean and cxfrs components should honour jax-rs providers in the bean registry
Date Sat, 11 Sep 2010 05:18:41 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher Hunt updated CAMEL-3117:
------------------------------------

    Summary: cxfbean and cxfrs components should honour jax-rs providers in the bean registry
 (was: cxfrs components should honour providers in the bean registry)

> 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.


Mime
View raw message