Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4152109B2 for ; Tue, 2 Jul 2013 05:51:53 +0000 (UTC) Received: (qmail 34529 invoked by uid 500); 2 Jul 2013 05:51:53 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 34291 invoked by uid 500); 2 Jul 2013 05:51:44 -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 34262 invoked by uid 99); 2 Jul 2013 05:51:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 05:51:41 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of agrawal.tarun23@gmail.com designates 209.85.128.174 as permitted sender) Received: from [209.85.128.174] (HELO mail-ve0-f174.google.com) (209.85.128.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 05:51:36 +0000 Received: by mail-ve0-f174.google.com with SMTP id oz10so4524836veb.19 for ; Mon, 01 Jul 2013 22:51:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=dPHK5hMeyq3zzriafb3kTnp43roSM9gzATGf/me0w4U=; b=ZoTdr4PH9yhuDdSYQlInqzTzv/JUyOl7/VALn9GrQhzUkBdh0AqIKQk2BxgZF78sOM uml8zEhSr/0+nNHUHd3WPXCdTSNWF2C55dQCB9WohFCWQf3ifqN+BderlmYC31i97wHU NVJ2xDdjS6IoMAC9JGDQTjOMgh12vw5EYiIlJVugDCYofARpw703mvQGaYJYdOycKskd mLIVKYw5RBxt5zh7UXuqYu4SRFfawP9xwWx+Yciwf0bjbyeishRV2kgVAW1thPLFi2ml KOzjfgLD+HRcth+em1I5dEBqm6c4zfr/+bZI49zmfvQTOGvzI5uIO991R4PFcSr/C2iA i33g== X-Received: by 10.58.234.161 with SMTP id uf1mr10624640vec.57.1372744275764; Mon, 01 Jul 2013 22:51:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.239.207 with HTTP; Mon, 1 Jul 2013 22:50:55 -0700 (PDT) From: Tarun Kumar Date: Tue, 2 Jul 2013 11:20:55 +0530 Message-ID: Subject: Is onFinally() compulsory after doCatch()? To: users Content-Type: multipart/alternative; boundary=047d7b6d7a9aecaf6904e080ee8f X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6d7a9aecaf6904e080ee8f Content-Type: text/plain; charset=ISO-8859-1 my route looks like this: from(). .toTry().process() .doCatch(Exception.class) .to().to().process() .end() My questions are: 1. is .doFinally compulsory after doCatch()? 2. In my case, how does route know whether second .to() in line 4 is inside doCatch() or after doCatch()? 3. I am using cxfrs component, why is my exchange body not being returned back to caller. Caller is seeing 204 no content found. While, when i remove doTry and doCatch() with same code, caller is able to see proper response (exchange body, status and all). Why is that? --047d7b6d7a9aecaf6904e080ee8f--