Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 37388 invoked from network); 5 Nov 2001 18:05:09 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 5 Nov 2001 18:05:09 -0000 Received: (qmail 5380 invoked from network); 5 Nov 2001 18:07:35 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 5 Nov 2001 18:07:35 -0000 Received: (qmail 463 invoked by uid 97); 5 Nov 2001 18:04:29 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 447 invoked by uid 97); 5 Nov 2001 18:04:28 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 436 invoked from network); 5 Nov 2001 18:04:28 -0000 Message-ID: <20011105180429.92957.qmail@web20910.mail.yahoo.com> Date: Mon, 5 Nov 2001 18:04:29 +0000 (GMT) From: =?iso-8859-1?q?Janek=20Bogucki?= Subject: Re: Included ( JSP not being recompiled To: Tomcat Users List MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --- Sriram Narayanan wrote: > > Modifying the JSP which includes the other JSP with > The changed included jsp will be noticed only when > the main JSP has to be recompiled. > -> when the main.jsp is changed does not cause 'not-getting-recompiled.jsp' to get recompiled. I retested this under Tomcat 4.0. 1. Modifying the included JSP does not cause it to be recompiled. 2. Modifying the JSP which includes the non-recompiling JSP does not cause the non-recompiling JSP to recompile. I would categorise this as a non-useful feature. Does the JSP spec have any to say on the conditions under which a JSP should be recompiled. Janek --- Sriram Narayanan wrote: > Hi, > > Since the main JSP has not changed, Tomcat will > continue to serve the main JSP's compiled code. > > The changed included jsp will be noticed only when > the main JSP has to be recompiled. > -> when the main.jsp is changed > -> when the work directory is emptied > > Sriram > > 05/11/2001 5:20:56 AM, Janek Bogucki > wrote: > > >I seem to have a problem with Tomcat not recompling > a > >changed JSP when the JSP is only used as an > included > >file with . > > > >I have a page which includes another JSPs: > > > >/MyJSP.html: > > > ><%@ page errorPage="/error.html" %> > > > >... > > >flush="true" /> > >... > > > > > > > >This is my included file, just static HTML: > > > >/_include/st.html#header.jsp: > > > > > > > > > >If 'MyJSP.html' is modified it's recompiled and > served > >out okay. However if '/_include/st.html#header.jsp' > is > >modified 'MyJSP.html' continues to use the old > version > >until I forced a recompile of > >'/_include/st.html#header.jsp' by deleting the > >out-of-date class from /work. > > > >Is there anything I can do to get > >'/_include/st.html#header.jsp' to recompile > >automatically when it's modifed? > > > >Thanks, > >Janek Bogucki > > > > > > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe: For additional commands: Troubles with the list: