You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/11/21 03:05:03 UTC

DO NOT REPLY [Bug 14725] New: - "Examples" webapp uses non-serializable session attributes

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=14725>.
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=14725

"Examples" webapp uses non-serializable session attributes

           Summary: "Examples" webapp uses non-serializable session
                    attributes
           Product: Tomcat 4
           Version: 4.1.12
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Webapps:Examples
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: ruvinsky@yahoo.com


Components of examples.war should only use serializable session attributes.  
(As an aside, IMO the session manager should have its "distributable" mode 
enabled by default.)  As an example, numguess.jsp stores the currently non-
serializable class num.NumberGuessBean in session scope.  The standard Tomcat 
session does not even persist the non-serializable attributes (and silently 
skips them if the manager is not declared to be "distributable").  This should 
be the example for which others should code their apps by.  The examples webapp 
should thus attempt to store session attributes that are always serializable.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>