What is the best way to handle complex transaction in Tapestry? Up to this point I had a bunch of services that have @CommitAfter annotation on them, and then I have a method say addNewSomething() in which I call a create a bunch of objects all conected to each other and then call appropriate services to persist them. The obvious problem is that each persist is not depended on the next one as it should be.
So now I am trying to put @CommitAfter anotation on the method addNewSomething and this works in some cases (for adding for example, but not for deleting - when I have to delete some object/objects from DB). Not really sure why is that Anyway what whould be the best way to handle this? Should I maybe consider spring and @Transactional annotation. Also is OpenSessionInViewFilter something that should be used in tapestry? It is my understanding that this is used because we first load an object and then when in the tml we have a call to list of objects that are not loaded it will throw an exception. However this does not happen for me. What it does happen is that if I load an object but in some method that is called on say form submit I need a list it will then throw an exception, but OpenSessionInViewFilter does not help with that, right? So I am right to assume that tapestry-hibernate has its own version of OpenSessionInViewFilter? Cheers -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-Transactions-tp5713299.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
