I'm getting error messages while compiling JSPs at runtime inside Tomcat but not when I compile the same JSPs with the <jasper2> Ant task.
I've upgraded my Ant build to use the new <jasper2> tag (the org.apache.jasper.JspC class) instead of the old <jspc> tag that came with Ant. (It doesn't work with Tomcat 5.0.16.) All my JSPs compile fine with the new class.
However, when I actually put the JSPs in my webapp for Tomcat to compile, I get a few compilation errors. Note that I'm compiling my JSPs as a quality assurance step, not to ship precompiled Java classes. I'm trying to find errors at build time rather than run time.
The problem comes with a poorly-coded JSP include action like this:
<jsp:include page="/asset/search.jsp" flush="false" > </jsp:include>
I'll be the first to admit this is poor style, and I'm not too upset that Tomcat won't compile it. I can easily fix it by removing the trailing tag and making it an empty tag. However, my normal method of finding these types of errors is failing me -- my Ant JSP build.
This is my build.xml snippet:
<jasper2
uriroot="${install.servlets}"
webXmlFragment="${root.build}/jspc/generated_web.xml"
outputDir="${root.build}/jspc"
package="org.apache.jsp.oculan"
/>This is the error message I get from Tomcat: Expected "param" tag with "name" and "value" attributes
I've started combing through the Jasper code to find what's different when compiling inside Tomcat as opposed to inside Ant. I've looked through all the top-level Jasper wrappering code that gathers the compilation options, but nothing seems significantly different. None of the compile options seem to be relevant to this issue.
There must be something going on deeper in the actual JSP compilation code. Does anyone have any idea what's happening?
Thanks, Larry Karnowski
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
