[
https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100845#comment-16100845
]
Önder Sezgin commented on CAMEL-5356:
-------------------------------------
{{<convertBodyTo type="java.lang.String"/> }} in spring.xml file requires
customer converter development. (once convertBodyTo is removed, all tests pass
in camelTryAndCatch_now example. the issue is not related to try catch by the
looks of it. it is complete conversion issue.)
because cxf returns {{org.apache.cxf.message.MessageContentsList}} as an empty
list.
it is either required to write customer converter or accepting empty list
collection as non-convertable object.
as [~davsclaus] mentioned in github comment like _an empty collection should
still be convertable_, it is nice to have custom converter. the issue seems to
be invalidated. I propose closing it by marking 'not a problem'
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Assignee: Önder Sezgin
> Fix For: Future
>
> Attachments: camelTryCatch_now.zip, camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there
> are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is
> down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an
> error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario
> because, apprently, the CXF endpoint nulls the message when receiving an
> exception or fault.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
