tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berry, Layton" <>
Subject RE: <%@ include %> files and Jasper/Ant
Date Thu, 08 Jul 2004 21:08:17 GMT
Tomcat compiles pages as needed.  So if someone hits
File.jsp, the file is created and compiled.

If you were to hit FileB.jsp, Tomcat would try to compile
it and get the compile errors.

Your ant job is no doubt trying to compile all the .jsp files,
causing your compile errors.  Try giving FileB.jsp a different


>-----Original Message-----
>From: Robert Hunt []
>Sent: Thursday, July 08, 2004 11:28 AM
>Subject: <%@ include %> files and Jasper/Ant
>Importance: High
>I'm trying to use Ant (in stand-alone fashion) to build a set 
>of JSPs.  The
>JSPs compile, execute and serve up HTML fine when compiled under Tomcat
>5.0.25; only the "root" JSPs generate .java files.  Eg. 
>FileA.jsp contains a
><%@ include="FileB.jsp" %> directive.  When requested through 
>the Tomcat web
>server, only and FileA_jsp.class are created.
>However, when I run Ant (or JspC) from the command line (using 
>the sample
>Application Compilation" for build.xml), it creates both 
> and
> The build then fails because's 
>by itself fails
>without having the context of being code included in FileA.
>How do Jasper/Ant running behind the scenes under the Tomcat 
>webserver know
>not to emit and compile the dependent files?  And why would Jasper/Ant
>running standalone (I'm using Ant 1.6.1 as-is from the .ZIP 
>NOT produce same output?
>To unsubscribe, e-mail:
>For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message