[
https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100066#comment-16100066
]
ASF GitHub Bot commented on CAMEL-5356:
---------------------------------------
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1847
CAMEL-5356 - handle if the value is an empty collection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/onders86/camel CAMEL-5356
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1847.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1847
----
commit 2c654d97c7f4332ce1aa07b694be4bd12fd545f4
Author: onders86 <[email protected]>
Date: 2017-07-25T13:51:26Z
CAMEL-5356 - handle if the value is an empty collection
----
> 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)
