[
https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-5356:
-------------------------------
Fix Version/s: Future
Issue Type: Bug (was: Wish)
Lets see if we can get this fixed in a future patch releases of the Camel
branches.
In terms of #2 then the idea would be that when you use handleFault=true then
Camel turns SOAP Faults into exceptions, which try .. catch ought to react upon.
> 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
> Fix For: Future
>
> Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
