[
https://issues.apache.org/jira/browse/CAMEL-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267670#comment-14267670
]
Willem Jiang commented on CAMEL-8205:
-------------------------------------
Hi Sergey,
I think the way you just showed is workable, but the use case can be
implemented by a camel cxfrs proxy route just like this.
{code}
from("cxfrs:endpoint1").to("cxfrs:endpoint2").transform(xxx);
{code}
or
{code}
from("cxfrs:endpoint1")..transform(xxx).to("cxfrs:endpoint2");
{code}
If we want to modify the response, we could also change the implementation
directly. So I don't think it's a good idea to support user use the camel-cxfrs
endpoint this way.
For "to(cxfbean:serviceBean)", it can leverage the camel component to provide
some transports those CXF doesn't support, but I don't think people use it that
way.
> 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
> Assignee: Willem Jiang
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
