Thank you David, makes sense. Your email ended up in my spam folder, so have only just seen it.
________________________________ From: David E Jones <[email protected]> To: [email protected] Sent: Tuesday, April 14, 2009 9:04:32 PM Subject: Re: processorder + transaction boundires In general each event in a request chain runs in its own transaction and is responsible for returning a status according to its result, and then in the request response definitions you can decide how to have the request chain flow based on those responses. If you want it to be part of the transaction, then looking at the underlying service called and using an SECA rule to trigger your service is the better way to go. -David On Apr 14, 2009, at 5:40 AM, Grant Edwards wrote: > Hi, > > The processorder request is the first in a long chain of requests that form > the order pipe-line, which terminates with the ordercomplete view. > What is not clear to me is where if any are the transaction boundries. For > example if the storeOrder service were to fail would work done by all > requests in the order pipe-line be rolled back? > > Further to this, I have inserted a custom request into the order pipe-line > that does the following: > 1) Processes booking related info on a 3rd party system. > 2) Logs status information to the ofbiz database in a custom table. > > Here again would a rollback undo work done by point 2, and any ideas about > how best to intercept the rollback so that an "undo" method can be affected > on the 3rd parth system. > > Kind regards > > Grant > >
