Hi, thanks for answer. Please, can you provide link to this JIRA task for feedback?
On the other hand, what is the scenario when user want to have two same conversation method? Maybe when we have isolated modules? Nothing else I can think... Sometimes unexpected behavior of converter is if input parameter of converter is child of output parameter (is-a relation), because in this case the converter will not be used, because output parametr is instanse of input parameter. Yes, this is bad practise how to use converter but equally :) It would take a strict comparison I would like to say :) By the way, when converters (Camel) will support passing arguments of conversation method by standard annotation such as properties (@Property(propName)), headers (@Header(propName))and so on? Now, only not annotated Exchange is supported and I think it's pitty. Tomas -- View this message in context: http://camel.465427.n5.nabble.com/How-to-avoid-loading-the-same-types-of-converters-tp5753579p5753605.html Sent from the Camel Development mailing list archive at Nabble.com.
