u can also let Tapestry-Hibernate take care of that for u. On Fri, Nov 13, 2009 at 3:18 PM, Szemere Szemere <szemereszem...@googlemail.com> wrote: > Afaik any Hibernate object stored in the HTTPSession will be > Hibernate-detached between HTTP requests. It is not refreshed/merged > automatically on a new HTTP request, so it will be outside the Hibernate > session on the second request which is probably not what you want. > > It is generally a much better idea to store the object id in the session and > recreate it at the beginning of each new HTTP request. Tapestry has some > features to make this easy for you, but that's beyond my expertise (search > the mailing list). > > Szemere >
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
