Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Problem with Session serialization and Version checks

Description

Steps to repro:
1.) user comes, retrieves entity. in order to later use the functionality of staleobjectexception, I serialize the ISession, and save it to the HttpContext.Session for that user

2.) user modifies page data, presses save

3.) I deserialize the ISession from HttpContext.Session, and try to save the entity

and it does not work

Environment

None

Activity

Show:

Peter Smulovics 
February 17, 2005 at 6:09 AM

Couldn't repro.

MikeM 
November 16, 2004 at 11:42 AM

Peter Smulovics 
October 25, 2004 at 12:56 AM

Yeah, this is still about the lazy loaded collections not having an open connection. Now I use a hacked version of NHibernate, by not throwing the session is disconnected messages, but opening one

MikeM 
October 24, 2004 at 11:12 PM

Peter, is this related to the IM we had the other day? I also thought I remember you talking about using Disconnect before serializing a session...

Peter Smulovics 
September 15, 2004 at 7:25 AM

The specific problem I found with this was that when I deserialized the session, the connection was sometimes already closed, and nhibernate didn't know about this, so it broke at the next database management operation...

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Who's Looking?

Open Who's Looking?
Created September 15, 2004 at 7:09 AM
Updated February 17, 2005 at 6:09 AM
Resolved February 17, 2005 at 6:09 AM
Who's Looking?