Hi, I am Matías. As far I see, the tapestry persistant & transactional stuff is coupled with Hibernate, don't you?
I would like to know if there is any contribution to override in order to have a different Transaction Manager to use, or even more, another SessionManager.... I know that if I inject an org.hibernate.Session in my service I am wiring me with hibernate, but would like to have some middle-layer to be able to configure another session manager. Another point is the @CommitAfter annotation, if I'am not using Hibernate, it has no sense... The CommitAfterWorker is wired to it. Thank you in advance. Matías. -- View this message in context: http://old.nabble.com/Is-tapestry-coupled-with-Hibernate-API--tp27111015p27111015.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
