+1. That's a good improvement as it makes camel's behavior more predictable. Thanks Claus.
Hadrian On Jan 18, 2011, at 5:34 AM, Claus Ibsen wrote: > Hi > > See > https://issues.apache.org/jira/browse/CAMEL-3550 > > Frankly over the years we have seen end users with some issues due > type converters failed to load on startup. > Camel keeps running but it wont work as well because there is one a > selected few hardcoded type converters available. > > From Camel 2.3 onwards we did INFO logging by default how many > converters and so forth was able to load. > So you can spot the issue if it says 0. > > But still this isn't good enough, so I have implement a fail fast > feature into camel-core, when using the classpath scanning for type > converters. > > I have run a full test and all is good. Even the OSGi tests works. > With this change I hope we can alert end users in a better way that > there is an issue loading the type converters. > > > If anyone sees any problems with this then feedback is welcome. > > > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/
