Thiago H. de Paula Figueiredo wrote: > > I don't think it makes sense to mix tapestry-hibernate and spring-tx. If > you need something that tapestry-hibernate doesn't handle, use spring-tx > for that. >
That's not what I thought of (and what I've implemented). The implementation is tapestry-hibernate specific and has no Spring dependency. Thiago H. de Paula Figueiredo wrote: > > I'd like to see (maybe even write) a transaction manager package built on > Tapestry-IoC and using the EJB 3 annotations, with some way to support > other annotations too (including @CommitAfter and Spring's @Transactional. > That's a good idea - then you would have tapestry-tx, tapestry-tx-spring and tapestry-tx-hibernate. Still you would have to change HibernateSessionManagerImpl to support more than one Transaction and Session (something like https://github.com/derkoe/tapestry5/blob/transactions/tapestry-hibernate-core/src/main/java/org/apache/tapestry5/internal/hibernate/HibernateSessionManagerImpl.java). -- Chris -- View this message in context: http://tapestry-users.832.n2.nabble.com/Transactional-needed-in-tapestry-hibernate-tp5826487p5828247.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
