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: local policy)
Message-ID: <4AF51D9D.6020602@die-schneider.net>
Date: Sat, 07 Nov 2009 08:11:25 +0100
From: Christian Schneider <chris@die-schneider.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Exception handling ... onException
References: <26215607.post@talk.nabble.com>
 <5380c69c0911050654j191e5e10taf050290759bdec5@mail.gmail.com>
 <26222792.post@talk.nabble.com>
In-Reply-To: <26222792.post@talk.nabble.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I have also woked with the onException clause recently and it worked for 
me. I used the spring dsl though.
It surely would help if you can create a small example project that 
shows your problem and post it for example
to a jira ticket. Once there is some code that can be debugged it is 
ususally quite easy to find a solution.

Greetings

Christian


DRy schrieb:
> Hi,
>
> we use one of the latest 2.1 snapshots (I will have a look at the exact date
> tomorrow).
>
> We use the onException-expressions (from the example below) in a
> RouteBuilder-class with one defined route. Both onException are placed
> before the route definition. So far the scope is global.
>
>
> DRy
>
>
> Claus Ibsen-2 wrote:
>   
>> What version of Camel are you using?
>>
>> And do you use global or route scoped onException ?
>>
>> On Thu, Nov 5, 2009 at 3:28 PM, DRy <dirk.rybinski@itellium.com> wrote:
>>     
>>> Hi,
>>>
>>> if I use two onException expressions in a route definition like this
>>>
>>>        onException(UnmarshalException.class)
>>>            .useOriginalBody()
>>>            .handled(true)
>>>                .bean(exceptionLogBean)
>>>                .process(new Publish2CenterExceptionBean())
>>>            .end();
>>>
>>>        onException(Exception.class)
>>>            .maximumRedeliveries(-1).redeliveryDelay(1000)
>>>            .useOriginalBody()
>>>            .handled(true)
>>>                .bean(exceptionLogBean)
>>>            .rollback()
>>>            .end();
>>>
>>> I got two problems:
>>>
>>> 1)
>>> The onEception(Exception.class) part is used all the time! Even if an
>>> UnmarshalException (direct hit) is thrown. And no matter if I put
>>> onException(Exception.class)... before
>>> onException(UnmarshalException.class)... ... ?
>>>
>>> 2)
>>> On the onException(Exception.class) part the bean(exceptionLogBean) is
>>> never
>>> called ... ?
>>>
>>> What I try to do is, to handle all "known" exception in seperate
>>> onException(...) parts and install a "last line of defence" with the
>>> onException(Exception.class).
>>>
>>>
>>> DRy
>>>       
>
>