I think wire tap actually serves me well. I have NOT verified that the execution of the SEDA route happens asynchronous when I set waitForTaskToComplete to Never. For now, I give it the benefit of the doubt ;). How would use futures be different from wire tapping?
Thanks a lot. On Fri, Jun 6, 2014 at 3:21 PM, kraythe . <[email protected]> wrote: > It would be interesting to implement asynch and share unit of work by way > of futures in the ... well ... future. :) But currently you cant really do > that. What you need are transactions. The problem is SEDA doesn't support > transactions. So what you need is JMS. > > *Robert Simmons Jr. MSc. - Lead Java Architect @ EA* > *Author of: Hardcore Java (2003) and Maintainable Java (2012)* > *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 > <http://www.linkedin.com/pub/robert-simmons/40/852/a39>* > > > On Fri, Jun 6, 2014 at 6:00 AM, Claus Ibsen <[email protected]> wrote: > > > Hi > > > > Maybe its the wire tap eip you should use. > > > > On Fri, Jun 6, 2014 at 12:38 PM, Max Bridgewater > > <[email protected]> wrote: > > > Hi Claus, > > > > > > Thanks for your input. Do you suggest to use synchronous flag on the > > SEDA > > > and VM producers? They have a flag waitForTaskToComplete that I > curretly > > > set to Never. Indeed if I set these flags to Always, the processing > > becomes > > > synchronous and everything works fine. The challenge is that these SEDA > > and > > > VM tasks take long to complete and I do not want them to impact > response > > > time. So, the question thus is if I can still have the SEDA and VM > > process > > > asynchronously and ignore by Unit of Work. > > > > > > Regards, > > > Max. > > > > > > > > > On Fri, Jun 6, 2014 at 6:16 AM, Claus Ibsen <[email protected]> > > wrote: > > > > > >> Hi > > >> > > >> You can set the synchronous option. See > > >> http://camel.apache.org/asynchronous-routing-engine.html > > >> > > >> On Fri, Jun 6, 2014 at 12:11 PM, Max Bridgewater > > >> <[email protected]> wrote: > > >> > Hi, > > >> > > > >> > I have a restlet route that triggers SEDA and VM routes. The unit of > > work > > >> > is used to do some transformation of the result before it is sent to > > the > > >> > HTTP client. It works fine as long as there is no SEDA or VM. As > soon > > as > > >> > the latter two are included, the unit of work is not executed > anymore. > > >> > > > >> > This seems to be related to the following thread: > > >> > > > >> > > > http://grokbase.com/t/camel/users/13856jw2j0/unit-of-work-scope-and-direct-seda-vm-components > > >> > > > >> > My question: how can I tell camel to simply ignore async routes such > > that > > >> > they do not impact unit of work. > > >> > > > >> > Thanks. > > >> > Max. > > >> > > >> > > >> > > >> -- > > >> Claus Ibsen > > >> ----------------- > > >> Red Hat, Inc. > > >> Email: [email protected] > > >> Twitter: davsclaus > > >> Blog: http://davsclaus.com > > >> Author of Camel in Action: http://www.manning.com/ibsen > > >> hawtio: http://hawt.io/ > > >> fabric8: http://fabric8.io/ > > >> > > > > > > > > -- > > Claus Ibsen > > ----------------- > > Red Hat, Inc. > > Email: [email protected] > > Twitter: davsclaus > > Blog: http://davsclaus.com > > Author of Camel in Action: http://www.manning.com/ibsen > > hawtio: http://hawt.io/ > > fabric8: http://fabric8.io/ > > >
