• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • Sessions
  • teck
  • Reporter: teck
  • March 01, 2007
  • 0
  • Watchers: 0
  • July 27, 2012
  • March 10, 2007


Web apps use request.getSession(..) to get a handle to the session object. When DSO sessions are used, the actual instance returned to the application is a wrapper/facade to the “real” session. That facade object cannot be made portable…..

So if an app tries to reference the session object from an attribute in the session, things won’t work.

An example of something that doesn’t work (but should):

session.setAttribute(“my session reference”, session);


Fiona OShea 2007-03-02

Did this really happen or is it hypothetical?

Tim Eck 2007-03-02

I’m going to move this into Moraga for the time being. No promises, but I want to try to look at it sooner

Tim Eck 2007-03-02

I’ve seen two instances of this so far, both in web frameworks (echo2 and jetspeed). I found the latter example while debugging things with a customer