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.
