Hello Claus, thanks for your very rapid reply!
I guess I could do that, but I'd prefer to keep my beans decoupled from Camel itself. Also because I'm using Spring component scanning to have my beans instantiated so then I'd have to annotate my beans with the @Depends-on annoation which is kinda ugly. Do you happen to know of any other solution? Also, isn't this a Camel bug? Camel could/should prevent Spring from shutting down beans used in routebuilders before the routebuilders are shutdown, no? Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Singleton-bean-creation-not-allowed-while-the-singletons-of-this-factory-are-in-destruction-during-sn-tp5713684p5713691.html Sent from the Camel - Users mailing list archive at Nabble.com.
