camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9864) Calling getBody(String.class) can break a simple Camel CXF proxy route
Date Wed, 13 Apr 2016 09:36:25 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238957#comment-15238957
] 

Akitoshi Yoshida commented on CAMEL-9864:
-----------------------------------------

I am looking into it...


> 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
>             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)

Mime
View raw message