camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: How to avoid loading the same types of converters
Date Wed, 09 Jul 2014 13:28:07 GMT

Good question. I think we have a JIRA ticket about adding a choice, so
users can control if they want Camel to
- fail for duplicates
- keep the oldest
- keep the newest (i think this is the model today)
- something else ???

As we got so many components now, its maybe time to get worked on this.

On Wed, Jul 9, 2014 at 11:56 AM, hanusto <> wrote:
> Hi,
> situation: Camel Context contains many and many routes and therefore many
> types of converters. But if we have two different converters (different
> package, name and so on), but with same signature of method and with same
> return types, unexpected behavior of Camel and TypeConverterRegistry is that
> only first converter that is loaded by AnnotationTypeConverterLoader
> (probably by order which class was loaded at first by class loader) is taken
> into account during dynamic inference and the others are ignored.
> Does anyone have any idea how to stop it? For example simply by
> configuration of camel context which throws exception if this collision will
> be discovered?
> Thanks, Tomas
> --
> View this message in context:
> Sent from the Camel Development mailing list archive at

Claus Ibsen
Red Hat, Inc.
Twitter: davsclaus
Author of Camel in Action:

View raw message