Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A30CC200CD0 for ; Tue, 25 Jul 2017 23:53:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A177316763A; Tue, 25 Jul 2017 21:53:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E72621676FA for ; Tue, 25 Jul 2017 23:53:09 +0200 (CEST) Received: (qmail 2725 invoked by uid 500); 25 Jul 2017 21:53:09 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 2716 invoked by uid 99); 25 Jul 2017 21:53:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2017 21:53:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 839DEC0412 for ; Tue, 25 Jul 2017 21:53:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id xoEiBhIqX-MK for ; Tue, 25 Jul 2017 21:53:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 939CF5FD7E for ; Tue, 25 Jul 2017 21:53:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8B645E065D for ; Tue, 25 Jul 2017 21:53:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 724E523F4F for ; Tue, 25 Jul 2017 21:53:02 +0000 (UTC) Date: Tue, 25 Jul 2017 21:53:02 +0000 (UTC) From: =?utf-8?Q?=C3=96nder_Sezgin_=28JIRA=29?= To: issues@camel.apache.org Message-ID: In-Reply-To: References:

Subject: [jira] [Commented] (CAMEL-5356) CXF endpoint doesn't play nice with doTry/doCatch MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 25 Jul 2017 21:53:10 -0000 [ https://issues.apache.org/jira/browse/CAMEL-5356?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1610= 0845#comment-16100845 ]=20 =C3=96nder Sezgin commented on CAMEL-5356: ------------------------------------- {{ }} 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 em= pty list. it is either required to write customer converter or accepting empty list c= ollection as non-convertable object. as [~davsclaus] mentioned in github comment like _an empty collection shoul= d still be convertable_, it is nice to have custom converter. the issue see= ms 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: =C3=96nder Sezgin > Fix For: Future > > Attachments: camelTryCatch_now.zip, camelTryCatch.zip > > > When using a CXF client endpoint to call a web service via SOAP/HTTP ther= e 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 a= n error condition to the application. > Currently, using doTry/doCatch doesn't work properly in either scenario b= ecause, apprently, the CXF endpoint nulls the message when receiving an exc= eption or fault. -- This message was sent by Atlassian JIRA (v6.4.14#64029)