Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Message-ID: <2133028536.1230979565395.JavaMail.jira@brutus>
Date: Sat, 3 Jan 2009 02:46:05 -0800 (PST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-1218) onException DSL should only be
 possible to set at top level (not within routes)
In-Reply-To: <1951416570.1230977765400.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48435#action_48435 ] 

Claus Ibsen commented on CAMEL-1218:
------------------------------------

The Spring DSL is a bit trickier to get fixed as onException is a processortype itself to allow routing. And the XSD is autogenerated based on JAXB annotations.

Jonathan is good at this, so I link it to the spring DSL ticket we have

> onException DSL should only be possible to set at top level (not within routes)
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-1218
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1218
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.5.1, 2.0.0
>
>
> The ErrorHandlerBuilder is global per route context so the DSL should only allow you to set it at highest level to avoid confusing end users.
> So this should *not* be allowed:
> {code}
>                 from("direct:start")
>                     .onException(MyTechnicalException.class).handled(true).end()
>                     .to("bean:doSomething");
> {code}
> But you need to do it as:
> {code}
>                 onException(MyTechnicalException.class).handled(true);
>                 from("direct:start")
>                     .to("bean:doSomething");
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.