beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kyle Marvin (JIRA)" <>
Subject [jira] Resolved: (BEEHIVE-194) ServletBeanContext is partially Serializable
Date Tue, 01 Feb 2005 23:48:17 GMT
     [ ]
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:
>      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?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message