Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <33344110.33091295347303644.JavaMail.jira@thor>
Date: Tue, 18 Jan 2011 05:41:43 -0500 (EST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-3550) Fail starting Camel if
 AnnotationTypeConverterLoader could not load any type converters
In-Reply-To: <15951172.28921295330982910.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen resolved CAMEL-3550.
--------------------------------

    Resolution: Fixed

trunk: 1060291.

> Fail starting Camel if AnnotationTypeConverterLoader could not load any type converters
> ---------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3550
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3550
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>
> When using Camel the type converters is loaded on the classpath using {{AnnotationTypeConverterLoader}}. We should let it thrown an exception if it could not find any type converters as it would cause Camel to startup with a very few type converter. This causes problems for end users when the cannot easily convert from XML-String, File-String etc.
> This can happen in runtimes such as OSGi, JBoss, or other containers where classloading can play tricks.

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