[
https://issues.apache.org/jira/browse/CAMEL-14391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013403#comment-17013403
]
Claus Ibsen commented on CAMEL-14391:
-------------------------------------
You need to provide a sample project / unit test or something that reproduces
this, and also discuss this first on the user mailing list.
> DefaultCxfBinding unable to pass on the camel exchnage body to soap response
> body after migrating from 2.x to 3.x
> -----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-14391
> URL: https://issues.apache.org/jira/browse/CAMEL-14391
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 3.0.0
> Reporter: Madhav
> Priority: Major
>
> We are trying to migrate from 2.x (2.24.1) to 3.0.0.
> We have a cxfEndpoint routed to camel route . So camel exchange headers and
> body are populated to soap response accordingly. It was working fine, but
> after upgrade defaultCxfbinding (which i believe is responsible class for
> this), is unable to pass it on. Hence soap response always comes empty.
>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
> <soap:Body/>
> </soap:Envelope>
>
>
> DataFormat is PAYLOAD.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
