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 Mon, 24 Jun 2002 14:45: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





------- Additional Comments From jspiewak@axeda.com  2002-06-24 14:45 -------
BEA seems to want to serialize all attribute scopes, even though the spec only 
requires it for session.  And no, there does not seem to be a way to turn it 
off.

However, even if it were possible to turn it off, it would not fix Struts.  If 
a class declares itself to be Serializable, all its fields must be Serializable 
themselves, or be declared transient.  Since Log (and SimpleLog) is not 
Serializable, any class that has a reference to Log must either not be 
Serializable (probably not what you want), or must declare its reference to be 
transient and do whatever work is needed to regenerated that reference after 
being deserialized.  Of course, the third alternative is to make Log 
Serializable.  With the exception of Log, the other cases mentioned can be 
fixed by making an object Serializable.  So it boils down to how you would like 
to deal with Log.

--
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