If the reloading is not quick enough.. you can always force reload by using the manager in Tomcat. http://jakarta.apache.org/tomcat/tomcat-4.0-doc/manager-howto.html
-Tim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 06, 2001 4:21 AM To: [EMAIL PROTECTED] Subject: jsp changes in Tomcat Tomcat is able to detect changes operated on a jsp. In fact when you point your browser to a jsp just modified it retranslates such a jsp and ricompiles the generated servlet, so you get the newer jsp. There is an exception, however. After jsp has been modified, Tomcat takes some time to recognize that jsp changed. (In my case it takes 5 seconds.) So pointing through a browser to a modified jsp within such time interval, Tomcat doesn't recognize jsp has newer version, and doesn't retranslate it, and you get the older version. I know I might delete the genereted .class file or change the name of the jsp to overcame the problem, but in my application I can't. Have you any idea? Is it a bug? Help me. ThanksN<����r�>zǧu�sS[h-+-��ڲ�ܢf�v)�-�^S{ay� �?�...�z�ƠzȠz?�HDU,D�51 $���b��!�����?+6�j˧r?�j�!S���ǫ�W�S{^��-?٥E�(�� �m���j���w(>�k��oe�� �z��z�����kz�.�Ǭ?٥,""HDU �i?�i��0�[(~�(>�sz楳��z���� ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
