Yes, that concept is similar to what I've seen done in 2+ places with custom scopes.
e.g. If you rely heavily on queue transports, you set the request Id for the scope to be the correllation Id (or Message Id or UUID if you have neither), and the "route" scope ends when the output message goes to the output queue. I can code this, but it sounds like it may be built-in. I was hoping that Claus could comment. -- View this message in context: http://camel.465427.n5.nabble.com/to-bean-xxx-or-not-to-bean-xxx-Getting-clarity-on-bean-scope-tp5754593p5754685.html Sent from the Camel - Users mailing list archive at Nabble.com.
