Re: Transaction Support in osWorkflow
"Pat Lightbody" <[email protected]>
| Newsgroups | gmane.comp.java.open-symphony.devel |
|---|---|
| Message-ID | <055101c32991$71cca6a0$6401a8c0@moose> |
rolling back the TX is something your functions (business logic) may need to do, but I have never seen a case where starting or commiting a TX is something the business logic needed to be concerned with. -Pat ----- Original Message ----- From: "Philipp Hug" <[email protected]> To: "Philipp Hug" <[email protected]>; "Pat Lightbody" <[email protected]>; "Mike Cannon-Brookes" <[email protected]>; "opensymphony-developers" <[email protected]> Sent: Monday, June 02, 2003 8:47 AM Subject: Re: [Opensymphony-developers] Transaction Support in osWorkflow > Can anyone explain, why the setRollbackOnly is in the WorkflowContext class > and the other 2 transaction functions in Workflow? > > philipp > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Opensymphony-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensymphony-developers ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5