[
https://issues.apache.org/jira/browse/CAMEL-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277177#comment-14277177
]
Sergey Beryozkin commented on CAMEL-8205:
-----------------------------------------
Patch is on the way. Let me clarify again the use case.
A CXF user has implemented a JAX-RS service, example, a CustomerService which
queries or updates some database. The task is to migrate this service into
Camel.
Wriiting a Camel Processor to check the operation names, etc (typical CXFRS
processing) while a service implementation already exists is not really
acceptable.
Camel offers one solution, from:jetty to cxfbean:bean, however it is a
migration effort on its own compared to simply converting the existing CXF
jaxrs:server configuration with JAX-RS providers, interceptors, properties, etc
into a cxfrs: schema and avoiding introducing a new HTTP aware component
(jetty, etc) into a context.
The service invocation will be optional and hence this enhancement is
completely safe as far as the typical CXFRS flow users are concerned.
CXFRS users will be able to work with the request properties as usual in custom
processors (example, also post a request body to some JMS topic, etc), while
having a portable JAX-RS service in place. The response body would also be
available to the custom processors.
Cheers, Sergey
> CXFRS Server should be able to invoke on JAX-RS service implementations
> ------------------------------------------------------------------------
>
> Key: CAMEL-8205
> URL: https://issues.apache.org/jira/browse/CAMEL-8205
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Reporter: Sergey Beryozkin
> Priority: Minor
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
