As suggested always configure each class name in that file. That makes the discovery easier at runtime as there is no package scanning happening which is not as good to perform, when you run in various different containers and environments with different class loading mehanism.
All the Camel components themselves configure all the class names in that TypeConverter file. http://camel.apache.org/type-converter On Wed, Apr 6, 2016 at 12:32 PM, kalber <karlheinz.al...@swslt.com> wrote: > ok, > > instead of full class name now i insert only the package in TypeConverter > file. > > So if i add a new converter i only must annotate class and method with > @Converter > an save in the configured package. > > > > > ----- > kh > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-2-17-Converter-auto-detection-tp5780578p5780582.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
