Hi, If you use Tapestry-Hibernate, it manages session for you, so there is only one session in one request, i don't think you have to merge them, just put @CommitAfter. one thing I notice, if table is MyIsam, it is always committed, for InoDB, u need @CommitAfter.
A.C Alfonso Quiroga wrote: > > Yes, I know, this should be in a hibernate mail-list, but I don't know > anyone, and I have a basic question > > I use T5 + hibernate, I have hibernate-session per web-request (it's > just a RequestFilter that closes the current hibernate session) > My question is this: > if I have a User object (or anything) in the Tapestry5 session... what > happens in diferent requests? I mean, if I have hibernate-session per > request, do I need to MERGE this objects with the current > hibernate-session? because this objects were created with another > hibernate session. Thanks! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > -- View this message in context: http://old.nabble.com/Hibernate-question-tp26314262p26314306.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
