Rick, what makes you think that the camel-salesforce or any other component "hijacks" headers? If you set a header - that is not used by this component - it should leave it untouched at the message.
However, if this is working there is no reason to have a stateful service thus avoiding issues with the scoping in the first place. If you're injecting a header-value (primitive type or POJO ...) in your handler/service it will be the object you've put in. No need to hope. Regards, Michael On Wed, Jul 30, 2014 at 12:21 AM, rickaroni <rgfa...@directv.com> wrote: > Hiya, > > Yeah, but I think that assumes that components will be thoughtful enough to > pass me what I want back. > > If a component (e.g. camel-salesforce) needs both the header and body for me > to make a request-response, I have to hope that it passes me the service bean > instance (that's also in the exchange) back, no? > > Rick > > From: David J. M. Karlsen [via Camel] > [mailto:ml-node+s465427n5754612...@n5.nabble.com] > Sent: Tuesday, July 29, 2014 4:49 PM > To: Fanta, Richard G > Subject: Re: <to "bean:xxx" or not <to "bean:xxx" .... - Getting clarity on > bean scope > > 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 <[hidden > email]</user/SendEmail.jtp?type=node&node=5754612&i=0>>: > >> 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 > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://camel.465427.n5.nabble.com/to-bean-xxx-or-not-to-bean-xxx-Getting-clarity-on-bean-scope-tp5754593p5754612.html > To unsubscribe from <to "bean:xxx" or not <to "bean:xxx" .... - Getting > clarity on bean scope, click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5754593&code=cmdmYW50YUBkaXJlY3R2LmNvbXw1NzU0NTkzfDUwOTA4Mjcz>. > NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/to-bean-xxx-or-not-to-bean-xxx-Getting-clarity-on-bean-scope-tp5754593p5754613.html > Sent from the Camel - Users mailing list archive at Nabble.com.
