[
https://issues.apache.org/jira/browse/CAMEL-9864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239141#comment-15239141
]
Christian Schneider commented on CAMEL-9864:
--------------------------------------------
In any case after your explanations I would say this is not a bug in camel.
Rather a missinterpretation on how it works on our side. The only thing is that
the now failing code worked in camel 2.15. So it might be regarded as a
regression. Not sure though.
I will talk to our devs who originally found the issue and see if they are fine
with enabling stream caching or simply not using getBody without also setting
the body.
> Calling getBody(String.class) can break a simple Camel CXF proxy route
> ----------------------------------------------------------------------
>
> Key: CAMEL-9864
> URL: https://issues.apache.org/jira/browse/CAMEL-9864
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.16.3
> Reporter: Christian Schneider
> Assignee: Akitoshi Yoshida
> Fix For: 2.16.4
>
>
> A simple CXF proxy route like this works:
>
> from("cxf://http://localhost:8122/myservice_proxy?dataFormat=PAYLOAD&wsdlURL=classpath:/DemoService_0.1.wsdl";)
>
> .to("cxf://http://localhost:8121/myservice?dataFormat=PAYLOAD&wsdlURL=classpath:/DemoService_0.1.wsdl";)
> If you add a processor that simply reads the body then resulting route above
> will always return an empty body:
> .process(new Processor() {
>
> @Override
> public void process(Exchange exchange) throws Exception {
> exchange.getIn().getBody(String.class);
> }
> })
> I suspect this is a bug in the new stream caching as the code works in camel
> 2.15.x and the main difference in 2.16 is the added CachedCxfPayload.
> I will add a small github repo that shows the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
