Hi

Is there a recommanded pattern to use to allow long running user transactions using the open session in view pattern.
I read here and there that the second level cache may be the solution to my problem but although I will end up using it for performance reasons I wonder if there are any other ways of doing this.

What I do at the moment is get an entity and then store it in its entirety (not its id only) into an HttpSession variable. The reason I am doing this is to use the bidirectional binding support in Spring.Web.
Other way is to use separate nhibernate sessions from the main UI session to store "cached" entities but then I do have to develop connection pooling and such like...

Any idea?
Daniel