Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 38084 invoked from network); 29 Nov 2010 10:43:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Nov 2010 10:43:06 -0000 Received: (qmail 11775 invoked by uid 500); 29 Nov 2010 10:43:06 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 11743 invoked by uid 500); 29 Nov 2010 10:43:06 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 11735 invoked by uid 99); 29 Nov 2010 10:43:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Nov 2010 10:43:05 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Nov 2010 10:42:59 +0000 Received: from sam.nabble.com ([192.168.236.26]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1PN1Bu-0006qG-26 for users@camel.apache.org; Mon, 29 Nov 2010 02:42:38 -0800 Date: Mon, 29 Nov 2010 02:42:38 -0800 (PST) From: davsclaus To: users@camel.apache.org Message-ID: <1291027358057-3284193.post@n5.nabble.com> In-Reply-To: <1291021341669-3284089.post@n5.nabble.com> References: <1291021341669-3284089.post@n5.nabble.com> Subject: Re: How to unmarshal a soap response MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org What errors do you see when you do unmarshal? And a good idea is to look at some unit tests from camel-soap component. Camel will automatic throw an exception if HTTP status != 200. So you can use Camel error handling to cater for that. http://camel.apache.org/error-handling-in-camel.html You can even use doTry .. doCatch kinda logic -- View this message in context: http://camel.465427.n5.nabble.com/How-to-unmarshal-a-soap-response-tp3284089p3284193.html Sent from the Camel - Users mailing list archive at Nabble.com.