Re: Transaction Support in osWorkflow
"Pat Lightbody" <[email protected]>
| Newsgroups | gmane.comp.java.open-symphony.devel |
|---|---|
| Message-ID | <061301c3249f$e805cc80$6701a8c0@moose> |
Also note that WorkflowContext has a rollback method. -Pat ----- Original Message ----- From: "Mike Cannon-Brookes" <[email protected]> To: "opensymphony-developers" <[email protected]> Sent: Monday, May 26, 2003 5:55 AM Subject: Re: [Opensymphony-developers] Transaction Support in osWorkflow > Yep - with OFBiz and Hibernate these things are handled outside the OSWF > context too. Why would we want the interfaces inside it? Is there a > particular reason for it? > > Cheers, > Mike > > On 26/5/03 10:45 PM, "Hani Suleiman" ([email protected]) penned the words: > > > I'm somewhat against this. The ejb persistence layer provides tx > > management for free, and it seems somewhat silly to reinvent the wheel. > > > > On Monday, May 26, 2003, at 05:54 AM, Philipp Hug wrote: > > > >> Is anyone using transactions in osWorkflow? (except with ofbiz) > >> I'd like to add transaction functions to the persistence interface > >> (begin, > >> commit, rollback), so we could put some basic transaction > >> functionality into > >> BasicWorkflow and BasicWorkflowContext. > >> What do you think? > >> > >> philipp > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: ObjectStore. > >> If flattening out C++ or Java code to make your application fit in a > >> relational database is painful, don't do it! Check out ObjectStore. > >> Now part of Progress Software. http://www.objectstore.net/sourceforge > >> _______________________________________________ > >> Opensymphony-developers mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers > >> > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: ObjectStore. > > If flattening out C++ or Java code to make your application fit in a > > relational database is painful, don't do it! Check out ObjectStore. > > Now part of Progress Software. http://www.objectstore.net/sourceforge > > _______________________________________________ > > Opensymphony-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-developers > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > _______________________________________________ > Opensymphony-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensymphony-developers ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge