Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <005501c46521$ac23ccd0$0500005a@MrNat>
From: "Robert Hunt" <robert-hunt@comcast.net>
To: <tomcat-user@jakarta.apache.org>
Subject: <%@ include %> files and Jasper/Ant
Date: Thu, 8 Jul 2004 15:27:55 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org