[
https://issues.apache.org/jira/browse/CAMEL-14391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013499#comment-17013499
]
Madhav commented on CAMEL-14391:
--------------------------------
I dig down further, actually the issue is BaseTypeConverterRegistry fails to
find any type in the context. There is difference in context.
2.X its SpringCamelContext
3. X its SpringBootCamelContext
In the former case, it has quite higher number of type mapping present in the
defaultTypeConverter.
In the former case, during the fallback conversion, it somewhere find the java
class type (corresponds to the payload), but in later its not added in whatever
mappings are present in the context. Hence the response from
DefaultCxfBinding.getBodyFromCamel() returns null.
> 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)
