tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15086] New: - System.out from destroy goes to different place than init message
Date Wed, 04 Dec 2002 21:05:20 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=15086>.
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=15086

System.out from destroy goes to different place than init message

           Summary: System.out from destroy goes to different place than
                    init message
           Product: Tomcat 4
           Version: 4.1.16
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Servlet & JSP API
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: steve5m@yahoo.com


Suppose you have a jsp that prints a message to System.out from both
it's jspInit and jspDestroy methods.
The init message goes to the window where tomcat was started, but
the destroy message goes to the Tomcat log.
Shouldn't these to messages go to the same place? (either the window
or the log, or both -- but at least be consistent?)
The same issue exists with Servlets that have a init and destroy method.

I will attach a test war file. It contains two simple
jsp's (preload1.jsp, preload2.jsp) that print out messages to System.out
in both their jspInit and jspDestroy methods.
Also contains a Servlet that does the same kind of thing (init/destroy 
methods).
Reload the context a couple times and note where the messages go.

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


Mime
View raw message