Thanks Kyle! It was coming up in Portal -- I'm sure they'll be happy to
see the stacktraces go away.
Kyle Marvin (JIRA) wrote:
[ http://issues.apache.org/jira/browse/BEEHIVE-194?page=history ]
Kyle Marvin resolved BEEHIVE-194:
---------------------------------
Assign To: Rich Feit (was: Kyle Marvin)
Resolution: Fixed
Fix Version: V1Beta
Good catch, Rich. Made the request stack transient, and restructured access
to it so it should be properly re-initted if serialized/deserialized.
ServletBeanContext is partially Serializable
--------------------------------------------
Key: BEEHIVE-194
URL: http://issues.apache.org/jira/browse/BEEHIVE-194
Project: Beehive
Type: Bug
Components: Controls
Reporter: Rich Feit
Assignee: Rich Feit
Fix For: V1Beta
ServletBeanContext, which is stored in the session, keeps a stack of ServletBeanContext$RequestContext objects. ServletBeanContext is Serializable (through superclass BeanContextSupport), but RequestContext is not. This means that when the session is serialized, there can be errors because ServletBeanContext is not fully Serializable. I think the stack of RequestContexts (ServletBeanContext._reqStack) should be transient. It may be true that the stack of RequestContext objects is only nonempty in the middle of a request, but we can't guarantee that the session won't be serialized in the middle of a request (this is common with code that tests the size of the session).
Kyle, is this one yours?
