As long as your beans are just looking at the exchanges being passed to them and not changing them, I should think they wouldn't care about extra headers, unless they're specifically looking at all headers attached to an exchange.
Barring that, is there an identifying key in the transformed object that relates to the original object? If so, add a bean before the transformer (or modify the transformer) to save the key and the original object in a map, then add a bean at the end of the route to look up the key in the map and perform the delete? On Fri, Dec 14, 2012 at 1:21 PM, dmcamp <dimac...@gmail.com> wrote: > Thanks for the response David. > Is there any other way to accomplish what I need? > The thing is, I'm using business beans, and they are not coupled to camel > stuff, and I would like to keep it that way. > I was thinking maybe another approach is possible: > I would like that my endpoint which deletes the objects, sits after the one > who provides those objects, but at the same time waits until the endpoint > which sends then by email finishes. > Is that possible? > Thanks! > > 2012/12/14 David J. M. Karlsen [via Camel] < > ml-node+s465427n5724113...@n5.nabble.com> > >> Save the untransformed message in å header ør property >> Den 14. des. 2012 16:59 skrev "dmcamp" <[hidden >> email]<http://user/SendEmail.jtp?type=node&node=5724113&i=0>> >> følgende: >> >> > Hello All, >> > >> > I have the following situation: >> > In my camel route I'm sending an object, which is then transformed by an >> > endpoint, then the transformed object is sent by email by another >> endpoint, >> > and I want to put another endpoint after the last one which deletes the >> > original object from a DB. >> > How can I achieve this using camel? >> > >> > Object -> [Transformer - Endpoint 1] -> transformed Object -> [ Email >> > Sender >> > - Endpoint 2] -> ? -> [Delete Object - Endpoint 3] >> > >> > Thanks! >> > >> > >> > >> > -- >> > View this message in context: >> > >> http://camel.465427.n5.nabble.com/Access-a-previous-message-tp5724107.html >> > Sent from the Camel - Users mailing list archive at Nabble.com. >> > >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://camel.465427.n5.nabble.com/Access-a-previous-message-tp5724107p5724113.html >> To unsubscribe from Access a previous message, click >> here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5724107&code=ZGltYWNhbXBAZ21haWwuY29tfDU3MjQxMDd8LTk1NjI4NDcxOQ==> >> . >> 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/Access-a-previous-message-tp5724107p5724121.html > Sent from the Camel - Users mailing list archive at Nabble.com.
