Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <2178087.36761278660352834.JavaMail.jira@thor>
Date: Fri, 9 Jul 2010 03:25:52 -0400 (EDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-2920) more eager validation of routes
In-Reply-To: <18373268.34781278521031777.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/CAMEL-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2920.
--------------------------------

    Resolution: Fixed

bean and method call using ref now check on startup if the bean exists in the registry

trunk: 962430.

> more eager validation of routes 
> --------------------------------
>
>                 Key: CAMEL-2920
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2920
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.4.0
>
>
> it seems you can dynamically create invalid routes which don't fail fast if there are errors.
> e.g.
> {code}
> from("seda:foo").beanRef("doesNotExist", "noMethodCalledThis")
> {code}
> its only if a message is sent to "seda:foo" that the whole thing barfs. We should maybe check that the to can be validated first before allowing the consumer to startup? If nothing else failing faster and earlier helps users spot errors sooner

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