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 07:15:40 UTC
[jira] Created: (CAMEL-3117) cxfrs components should honour
instanted providers in the bean registry
cxfrs components should honour instanted 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.
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@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 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.
[jira] Updated: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Hunt updated CAMEL-3117:
------------------------------------
Attachment: providers.diff
Changes inclusive of a new test case to test the number of providers
> 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
> Assignee: Willem Jiang
> Attachments: providers.diff
>
>
> 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.
[jira] Issue Comment Edited: (CAMEL-3117) cxfbean and cxfrs
components should honour jax-rs providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@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.
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Sergey Zolotaryov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63195#action_63195 ]
Sergey Zolotaryov commented on CAMEL-3117:
------------------------------------------
To fix this I have to override a method in CxfRsEndpoint and do an ugly thing like this:
{code}
@Override
protected void setupJAXRSServerFactoryBean(final JAXRSServerFactoryBean sfb)
{
super.setupJAXRSServerFactoryBean(sfb);
final CamelContext context = getCamelContext();
if (context instanceof SpringCamelContext)
{
final SpringCamelContext camelContext = (SpringCamelContext) context;
final ApplicationContext applicationContext = camelContext.getApplicationContext();
final Map<String, Object> springProviders = applicationContext.getBeansWithAnnotation(Provider.class);
final List< ? > existingProviders = sfb.getProviders();
final ArrayList<Object> newProviders = new ArrayList<Object>(springProviders.values());
if (existingProviders != null)
{
newProviders.addAll(existingProviders);
}
sfb.setProviders(newProviders);
}
}
{code}
> 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
> Assignee: Willem Jiang
> Fix For: 2.5.0
>
> Attachments: providers.diff
>
>
> 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.
[jira] Updated: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61807#action_61807 ]
Willem Jiang commented on CAMEL-3117:
-------------------------------------
Also updated the wiki page and release note for it.
> 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
> Assignee: Willem Jiang
> Fix For: 2.5.0
>
> Attachments: providers.diff
>
>
> 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.
[jira] Resolved: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Hunt resolved CAMEL-3117.
-------------------------------------
Fix Version/s: 2.5.0
Resolution: Fixed
My patch resolves this issue and now provides a unit test. However I did just look at the unit test again and I think that line 36 of CxfBeanTest could benefit from a not-null check (even though no issue presented itself) i.e.
{code}
if (beanEndpoint.getProviders() != null) {
if (beanEndpoint.getProviders().size() == 2) {
testedEndpointWithProviders = true;
break;
} else if (beanEndpoint.getProviders().size() != 0) {
fail("Unexpected number of providers present");
}
}
{code}
> 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
> Assignee: Willem Jiang
> Fix For: 2.5.0
>
> Attachments: providers.diff
>
>
> 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.
[jira] Updated: (CAMEL-3117) cxfrs components should honour
providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Hunt updated CAMEL-3117:
------------------------------------
Summary: cxfrs components should honour providers in the bean registry (was: cxfrs components should honour instanted providers in the bean registry)
> cxfrs components should honour 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.
[jira] Assigned: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-3117:
-----------------------------------
Assignee: Willem Jiang
> 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
> Assignee: Willem Jiang
> Attachments: providers.diff
>
>
> 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.
[jira] Updated: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Hunt updated CAMEL-3117:
------------------------------------
Attachment: providers.diff
Code modifications to the cxfbean component so that the declaration of JAX-RS providers is made possible.
> 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
> Attachments: providers.diff
>
>
> 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.
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61806#action_61806 ]
Willem Jiang commented on CAMEL-3117:
-------------------------------------
Applied patch with thanks to Christopher.
I fixed the CS errors of the patch also add the assertNotNull check on the beanEndpoint.getProviders().
The up change will make the test pass if there is no provider is set to the beanEndpoint.
> 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
> Assignee: Willem Jiang
> Fix For: 2.5.0
>
> Attachments: providers.diff
>
>
> 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.
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63301#action_63301 ]
Willem Jiang commented on CAMEL-3117:
-------------------------------------
If you want to add the provider into the camel cxfrs endpoint, you need to do the thing like this
{code}
<cxf:rsServer id="rsServer" address="http://localhost:9000/router"
serviceClass="org.apache.camel.component.cxf.jaxrs.testbean.CustomerService">
<cxf:providers>
<ref bean="jsonProvider"/>
</cxf:providers>
</cxf:rsServer>
<bean id="jsonProvider" class="org.apache.cxf.jaxrs.provider.JSONProvider"/>
<!-- The camel route context -->
<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
<route>
<from uri="cxfrs://bean://rsServer"/>
<!-- We can remove this configure as the CXFRS producer is using the HttpAPI by default -->
<setHeader headerName="CamelCxfRsUsingHttpAPI">
<constant>True</constant>
</setHeader>
<to uri="cxfrs://bean://rsClient"/>
</route>
</camelContext>
{code}
> 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
> Assignee: Willem Jiang
> Fix For: 2.5.0
>
> Attachments: providers.diff
>
>
> 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.
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61776#action_61776 ]
Willem Jiang commented on CAMEL-3117:
-------------------------------------
Hi Christopher,
I just have a quick look at your patch, it looks good.
Can you add an unit test for it ? Then I'd happy to apply it for your :)
Willem
> 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
> Attachments: providers.diff
>
>
> 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.
[jira] Commented: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Sergey Zolotaryov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63194#action_63194 ]
Sergey Zolotaryov commented on CAMEL-3117:
------------------------------------------
Hello everybody.
I've been trying to add custom @Provider and I see that MessageBodyWriter is correctly applied, but I cannot by any means find my MessageBodyReader's in the context. I create a reader bean in spring context and it's still not used by my cxfrs endpoint.
> 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
> Assignee: Willem Jiang
> Fix For: 2.5.0
>
> Attachments: providers.diff
>
>
> 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.
[jira] Updated: (CAMEL-3117) cxfbean and cxfrs components should
honour jax-rs providers in the bean registry
Posted by "Christopher Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Hunt updated CAMEL-3117:
------------------------------------
Attachment: (was: providers.diff)
> 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
> Assignee: Willem Jiang
> Attachments: providers.diff
>
>
> 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.