Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 13 Jul 2011 15:01:01 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <447772480.10117.1310569261764.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1546520437.9563.1310558521516.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CAMEL-4222) Ref component should throw exception
 if bean not found in registry
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daniel Kulp updated CAMEL-4222:
-------------------------------

    Fix Version/s: 2.7.3

> Ref component should throw exception if bean not found in registry
> ------------------------------------------------------------------
>
>                 Key: CAMEL-4222
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4222
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.7.3, 2.8.0
>
>
> When you use the ref component and you refer to a non existing endpoint, then it silently returns null, causing Camel to fail with a different error saying the ref component cannot be found
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: ref://xxx due to: No component found with scheme: ref
> It should use mandatoryLookup, and those methods should throw NoSuchBeanException instead of IllegalArgumentException as they currently does. Then the failure message is much more precise.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira