Hi Antonin Very interesting (and elegant!) suggestion. I like the fact that - I can leave untouched the existing code - all the back/white-listing logic is concentrated into one single class (=the extension)
I agree with you, a @Conditional annotation should be generic (ie not restricted to properties). In the meantime, I was thinking of a third solution. Use "profile" like in Spring (again), ie: Anyway, thanks a lot for the hint. Regards, Bernard. Bernard. -- View this message in context: http://camel.465427.n5.nabble.com/Conditional-registration-of-routes-or-route-builders-tp5795589p5795599.html Sent from the Camel - Users mailing list archive at Nabble.com.
