Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1408554018572-5755450.post@n5.nabble.com>
References: <1408554018572-5755450.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 21 Aug 2014 08:07:03 +0200
Message-ID: 
 <CAGB5yN=CGXJpSB9J90rc9+ugfPEYr9D_j_XZr0oAyNVwP_rk1w@mail.gmail.com>
Subject: Re: Camel-Mybatis 2.13.1 CamelMyBatisStatementName not updated for
 failed statement
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi

No this is correct. Camel only updates the message if the process was succesful.

There is a property stored on the exchange with the failed endpoint you can use.

See section _which endpoint failed_ at
http://camel.apache.org/dead-letter-channel.html


On Wed, Aug 20, 2014 at 7:00 PM, sandp <sandeepreddip@gmail.com> wrote:
> I'm trying to insert the failed CamelMyBatisStatementName to DB and noticed
> that camel is not updating the header  CamelMyBatisStatementName with the
> statement name that failed.
>
> *Here's the scenario:*
> from("some endpoint")
>         .to("mybatis:mapper.statement1?statementType=Update")
>         .to("mybatis:mapper.statement2?statementType=Update")
>
> .to("mybatis:mapper.statement3?statementType=InsertList&executorType=batch")
> end();
>
> statement2  failed in the route above, but when I looked at the header
> CamelMyBatisStatementName, it still had the previously executed *statement1
> * name.
>
> I believe camel should update it with *statement2 * that actually failed as
> per the *Message Headers*  in  Camel MyBatis
> <http://camel.apache.org/mybatis.html>
>
>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-Mybatis-2-13-1-CamelMyBatisStatementName-not-updated-for-failed-statement-tp5755450.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/