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