Hi 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 <hanu...@gmail.com> 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: > http://camel.465427.n5.nabble.com/How-to-avoid-loading-the-same-types-of-converters-tp5753579.html > Sent from the Camel Development mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
