This is an ant script I wrote to precompile JSPs for tomcat, the benefit of this script, vs the regular precompile, is that is compiles files into the tomcat work folder, so there are no additions needed in web.xml and you can reload JSP files, and at the same time have the benefit of precompiled performance.
http://cvs.apache.org/~fhanik/precompile.html we have tons of include statements and they work fine. Not that this answers your question, but it may give you a better alternative Filip ----- Original Message ----- From: "Robert Hunt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 08, 2004 2:27 PM Subject: <%@ include %> files and Jasper/Ant > 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 FileA_jsp.java and FileA_jsp.class are created. > > However, when I run Ant (or JspC) from the command line (using the sample > from "http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jasper-howto.html#Web > Application Compilation" for build.xml), it creates both FileA_jsp.java and > FileB_jsp.java. The build then fails because FileB_jsp.java's compilation, > 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 distribution) > NOT produce same output? > > > --------------------------------------------------------------------- > 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]
