I think it rolls back only updateValues. I'd prefer to put several method calls under one transaction.
9902468 wrote: > > Hi, > > I'm trying to understand how transactions should be handled with the > @CommitAfter annotation. > > I have a normal service interface (FormDAO) that is annotated with commit > afters, but what happens when > > Pseudo code: > void onSave() { > > formDAO.saveForm(form); > formDAO.updateValues(form, user); > > } > > and the later call to formDAO throws an exception? Is the first method's > transaction also rolled back, even if both methods have their own > @CommitAfter annotations? > > The documentation doesn't specify whether the transaction is rolled back > if there is one successfull @CommitAfter and one failed. > > Is the correct approach to wrap multiple service calls in to one and > annotate only this? > > -99 > -- View this message in context: http://www.nabble.com/T5---Hibernate---Transaction-confusion-tp18826235p18826695.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]