Unfortunately I need to use the static include. (It defines methods and objects that most of my JSP pages use.)
If Jasper 2 can handle detection of static includes at run-time, why can't JSPC? >From the Tomcat 4.1 documentation: (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html) "Recompile JSP when included page changes - Jasper 2 can now detect when a page included at compile time from a JSP has changed and then recompile the parent JSP." -- Nathan Christiansen > -----Original Message----- > From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 04, 2004 9:19 AM > To: Tomcat Users List > Subject: RE: Tomcat 4.1 JSPC not recongnizing change in compile time > included file > > that is expected behavior. > <%@ include file="main.jsp"%> > is a static include, meaning, just copy and paste the file before > compilation. > if you had <jsp:include> then it should recognize the changes > > Filip > > -----Original Message----- > From: Nathan Christiansen [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 04, 2004 7:26 AM > To: [EMAIL PROTECTED] > Subject: Tomcat 4.1 JSPC not recongnizing change in compile time > included file > > > I am running Tomcat 4.1.24. > > In nearly all JSP files in my webapp I have the following compile time > include: > > <%@ include file="main.jsp"%> > > However, changes to main.jsp are not caught by JSPC. And only the > main_jsp.java source is changed. If I delete all the *_jsp.java files > and recompile all of the JSP files, it works perfectly. > > Anyone have any suggestions? > > > > I am using ant 1.5.3 with the following task segment in my build file: > > <jspc destdir="${jspc.src.jsp.dir}" > webinc="${jspc.base.dir}/fragment.xml" > package="jsp" > compiler="jasper41"> > <classpath> > <fileset dir="${publish.common.lib.dir}"> > <include name="ant.jar"/> > <include name="jasper-compiler.jar"/> > <include name="jasper-runtime.jar"/> > <include name="servlet.jar"/> > </fileset> > <pathelement path="${build.dir}"/> > </classpath> > <webapp basedir="${deploy.dir}"/> > </jspc> > > > I even tried calling JSPC directly using the task fragment described in > the Tomcat 4.1 documentation: > > <taskdef classname="org.apache.jasper.JspC" name="jasper2" > > <classpath id="jspc.classpath"> > <pathelement location="${java.home}/../lib/tools.jar"/> > <fileset dir="${tomcat.server.lib.dir}"> > <include name="*.jar"/> > </fileset> > <fileset dir="${publish.common.lib.dir}"> > <include name="*.jar"/> > </fileset> > </classpath> > </taskdef> > > <jasper2 > validateXml="false" > package="jsp" > uriroot="${deploy.dir}" > webXmlFragment="${jspc.base.dir}/fragment.xml" > outputDir="${jspc.src.jsp.dir}" /> > > > -- Nathan Christiansen > Software Engineer > Tahitian Noni International > http://www.tahitiannoni.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.594 / Virus Database: 377 - Release Date: 2/24/2004 > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.594 / Virus Database: 377 - Release Date: 2/24/2004 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
