Maybe create an instance and stick it into a camel header (the header will follow the exchange, and thus the lifecycle of passing through the route).?
2014-07-29 22:10 GMT+02:00 rickaroni <rgfa...@directv.com>: > Hi Michael, > > I hear you. The trouble is, sometimes the intermediate transports (e.g. > the > Camel Salesforce component) hijack the header and body for their own needs > and you don't have full control over them. > > In similar ESBs, I've seen some shops make their own custom Spring message > scope to be the lifetime of (the equivalent of) a route. > > That works pretty nicely when it's needed. I was hoping to avoid having to > write this myself, but can if needed. > > Thanks a lot, > Rick > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/to-bean-xxx-or-not-to-bean-xxx-Getting-clarity-on-bean-scope-tp5754593p5754609.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
