On 20 Dec (17:37), Mark Woon wrote:
Have you considered using a filter to close the Session after everything is rendered?
Yes, but closing/disconnecting the Session is _not_ the real problem.
The problem is: How and where does the Filter/Observer get and store the
Session to do its work?
Ah. I'm storing it in the request attributes. If a page needs a Session, it checks to see if one already exists in the request attributes. If it doesn't, it creates one and sticks it into the request attributes. At the end, the filter checks to see if the Session exists, and if so, closes it. Isn't this a relatively simple way of doing it?
-Mark
------------------------------------------------------- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
