Thanks! Testing before delivering is exactly what we're doing. :-) Our tests found that there was a difference between how camel 2.10 and camel 2.12 lookup and invoke methods that would cause our route to throw an exception because camel could no longer find the method we wanted to call in 2.12. It'd be great if instead of failing tests, we could have the service verify at initialization that it can find the dynamic methods it might use and have the route indicate an error when it is initialized vs when it's invoked.
Internally I'm guessing camel is parsing the string passed to method() and using that to get a Method instance that it then invokes. All we'd really need is access to whatever mechanism camel uses to get the Method instance and then at initialization time we could call this to validate the signatures of our dynamic methods. If we don't get a valid Method then we'd know something's wrong with the config before we even start testing. -e -- View this message in context: http://camel.465427.n5.nabble.com/Best-practice-for-checking-method-exists-on-class-when-building-route-tp5746752p5746818.html Sent from the Camel - Users mailing list archive at Nabble.com.
