Currently, there is only the @CommitAfter annotation in tapestry-hibernate. This is good for simple use cases but not sufficient for complex cases.
Imagine two services OrderService and CustomerService both storing the corresponding entities. Use case 1: Store a new customer without an order (register) Use case 2: Create a customer during an order processing process. If you have a @CommitAfter on the CustomerService the second use case is not really transactional. Therefore Spring introduced @Transactional, would this also make sense for tapestry-hibernate? I've done a basic implementation of that in a fork here: https://github.com/derkoe/tapestry5/tree/transactions (here are the changes https://github.com/derkoe/tapestry5/compare/trunk...transactions) What do you think? -- Chris -- View this message in context: http://tapestry-users.832.n2.nabble.com/Transactional-needed-in-tapestry-hibernate-tp5826487p5826487.html Sent from the Tapestry Users 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
