struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8487] - Serializability issues in ActionServlet/RequestProcessor
Date Tue, 23 Jul 2002 17:48:37 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8487>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8487

Serializability issues in ActionServlet/RequestProcessor

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From craig.mcclanahan@sun.com  2002-07-23 17:48 -------
The real problem is that the requirement for servlet context attributes to be
Serializable is totally bogus.  Containers that require this should be repaired.

Trying to support this "requirement" is not going to be feasible without a
complete architectural change in what gets stored as servlet context attributes.
 Simply making things like ActionServlet and RequestProcessor "implements
Serializable" -- and making all the needed instance variables transient --
doesn't work, because if the container actually does serialize and reload the
object, it will have all sorts of null values and will fail anyway.

I'm not planning on doing any more work to support this -- the J2EE specs only
require serializability on *session* attributes, and that's what Struts does for
the session attributes that it creates.

--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@jakarta.apache.org>


Mime
View raw message