2001-09-13 08:31:21 +00:00
|
|
|
<html>
|
|
|
|
|
|
|
|
|
|
<head>
|
|
|
|
|
<meta http-equiv="Content-Language" content="en-us">
|
|
|
|
|
<title>Ant User Manual</title>
|
|
|
|
|
</head>
|
|
|
|
|
|
|
|
|
|
<body>
|
|
|
|
|
|
|
|
|
|
<h2><a name="jspc">jspc</a></h2>
|
|
|
|
|
<h3>Description</h3>
|
|
|
|
|
|
|
|
|
|
<p> Ant task to run the jsp compiler.
|
2001-09-28 05:50:33 +00:00
|
|
|
<p>
|
2001-09-13 08:31:21 +00:00
|
|
|
|
2001-09-28 05:50:33 +00:00
|
|
|
It can be used to precompile jsp pages for fast initial invocation
|
|
|
|
|
of JSP pages, deployment on a server without the full JDK installed,
|
|
|
|
|
or simply to syntax check the pages without deploying them.
|
|
|
|
|
In most cases, a javac task is usually the next stage in the build process.
|
|
|
|
|
The task does basic dependency checking to prevent unnecessary recompilation -this
|
|
|
|
|
checking compares source and destination timestamps, and does not factor
|
|
|
|
|
in class or taglib dependencies.
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
|
|
|
|
|
The task needs jasper.jar and jasper-runtime.jar, which come with
|
|
|
|
|
builds of Tomcat 4/Catalina from the
|
|
|
|
|
<a href="http://jakarta.apache.org/tomcat/">Jakarta Tomcat project</a>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h3>Parameters</h3>
|
|
|
|
|
The Task has the following attributes:<p>
|
2001-09-13 08:31:21 +00:00
|
|
|
|
|
|
|
|
<table border="1" cellpadding="2" cellspacing="0">
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top"><b>Attribute</b></td>
|
|
|
|
|
<td valign="top"><b>Description</b></td>
|
|
|
|
|
<td align="center" valign="top"><b>Required</b></td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">destdir</td>
|
|
|
|
|
<td valign="top">Where to place the generated files. They are located
|
|
|
|
|
under here according to the given package name.</td>
|
|
|
|
|
<td valign="top" align="center">Yes</td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">srcdir</td>
|
|
|
|
|
<td valign="top">Where to look for source jsp files.</td>
|
|
|
|
|
<td valign="top" align="center">Yes</td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">verbose</td>
|
2001-09-28 05:50:33 +00:00
|
|
|
<td valign="top">The verbosity integer to pass to the compiler. Default="0"</td>
|
2001-09-13 08:31:21 +00:00
|
|
|
<td valign="top" align="center">No</td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">package</td>
|
|
|
|
|
<td valign="top">Name of the destination package for generated java
|
|
|
|
|
classes.</td>
|
|
|
|
|
<td valign="top" align="center">No</td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">ieplugin</td>
|
|
|
|
|
<td valign="top">Java Plugin classid for Internet Explorer.</td>
|
|
|
|
|
<td valign="top" align="center">No</td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">mapped</td>
|
|
|
|
|
<td valign="top">(boolean) Generate separate write() calls for each HTML
|
|
|
|
|
line in the JSP.</td>
|
|
|
|
|
<td valign="top" align="center">No</td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">classpath</td>
|
2001-09-28 05:50:33 +00:00
|
|
|
<td valign="top">The classpath to use to run the jsp compiler,
|
|
|
|
|
and bring in any tag libraries.
|
|
|
|
|
This can also be specified
|
|
|
|
|
by the nested element <code>classpath</code>
|
2001-09-13 08:31:21 +00:00
|
|
|
<a href="../using.html#path">Path</a>).</td>
|
|
|
|
|
<td valign="top" align="center">No</td>
|
|
|
|
|
</tr>
|
|
|
|
|
<tr>
|
|
|
|
|
<td valign="top">classpathref</td>
|
|
|
|
|
<td valign="top">A <a href="../using.html#references">Reference</a>. As
|
|
|
|
|
per <code>classpath</code></td>
|
|
|
|
|
<td valign="top" align="center">No</td>
|
|
|
|
|
</tr>
|
2001-09-28 05:50:33 +00:00
|
|
|
<tr>
|
|
|
|
|
<td valign="top">failonerror</td>
|
|
|
|
|
<td valign="top">flag to control action on compile failures: default=yes</td>
|
|
|
|
|
<td valign="top" align="center">No</td>
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
<P>The <tt>mapped</tt> option will, if set to true, split the JSP text content into a
|
|
|
|
|
one line per call format. There are comments above and below the mapped
|
|
|
|
|
write calls to localize where in the JSP file each line of text comes
|
|
|
|
|
from. This can lead to a minor performance degradation (but it is bound
|
|
|
|
|
by a linear complexity). Without this options all adjacent writes are
|
|
|
|
|
concatenated into a single write.</P>
|
|
|
|
|
|
|
|
|
|
<P>The <tt>ieplugin</tt> option is used by the <tt><jsp:plugin></tt> tags.
|
|
|
|
|
If the Java Plug-in COM Class-ID you want to use changes then it can be
|
|
|
|
|
specified here. This should not need to be altered.</P>
|
|
|
|
|
|
|
|
|
|
<h3>Parameters specified as nested elements</h3>
|
|
|
|
|
|
|
|
|
|
This task is a <a href="../dirtasks.html">directory based task</a>, like
|
2001-09-13 08:31:21 +00:00
|
|
|
<strong>javac</strong>, so the jsp files to be compiled are located as java
|
2001-09-28 05:50:33 +00:00
|
|
|
files are by <strong>javac</strong>. That is, elements such as <tt>includes</tt> and
|
|
|
|
|
<tt>excludes</tt> can be used directly inside the task declaration.
|
2001-09-13 08:31:21 +00:00
|
|
|
|
2001-09-28 05:50:33 +00:00
|
|
|
<p>
|
|
|
|
|
|
|
|
|
|
Elements specific to the jspc task are:-
|
|
|
|
|
|
|
|
|
|
<h4>classpath</h4>
|
|
|
|
|
|
|
|
|
|
The classpath used to compile the JSP pages is specified as for any other
|
|
|
|
|
classpath. Even if the jasper jars are in the ant library directory, or
|
|
|
|
|
are on the classpath in some other means, this element is important when
|
|
|
|
|
referring to tag libraries.
|
|
|
|
|
|
|
|
|
|
<h4>classpathref</h4>
|
|
|
|
|
a reference to an existing classpath
|
|
|
|
|
|
|
|
|
|
<h3>Example</h3>
|
2001-09-13 08:31:21 +00:00
|
|
|
<pre>
|
|
|
|
|
<jspc srcdir="${basedir}/src/war"
|
|
|
|
|
destdir="${basedir}/gensrc"
|
|
|
|
|
package="com.i3sp.jsp"
|
|
|
|
|
verbose="9">
|
2001-09-28 05:50:33 +00:00
|
|
|
<include name="**/*.jsp" />
|
2001-09-13 08:31:21 +00:00
|
|
|
</jspc>
|
2001-09-28 05:50:33 +00:00
|
|
|
</pre>
|
|
|
|
|
Build all jsp pages under src/war into the destination /gensrc, in a
|
|
|
|
|
package heirarchy beginning with com.i3sp.jsp.
|
|
|
|
|
<pre>
|
2001-09-13 08:31:21 +00:00
|
|
|
|
2001-09-28 05:50:33 +00:00
|
|
|
<jspc
|
|
|
|
|
destdir="interim"
|
|
|
|
|
verbose="1">
|
|
|
|
|
classpath="lib/taglibs.jar"
|
|
|
|
|
srcdir="src"
|
|
|
|
|
package="com.i3sp.jsp"
|
|
|
|
|
<include name="**/*.jsp" />
|
|
|
|
|
</jspc>
|
|
|
|
|
<depends
|
|
|
|
|
srcdir="interim"
|
|
|
|
|
destdir="build"
|
|
|
|
|
cache="build/dependencies"
|
|
|
|
|
classpath="lib/taglibs.jar"/>
|
|
|
|
|
<javac
|
|
|
|
|
srcdir="interim"
|
|
|
|
|
destdir="build"
|
|
|
|
|
classpath="lib/taglibs.jar"
|
|
|
|
|
debug="on" />
|
2001-09-13 08:31:21 +00:00
|
|
|
</pre>
|
2001-09-28 05:50:33 +00:00
|
|
|
Generate jsp pages then javac them down to
|
|
|
|
|
bytecodes. Include lib/taglib jar in the
|
|
|
|
|
JSP build and the compilation. Dependency checking is used to scrub the
|
|
|
|
|
java files if class dependencies indicate it is needed.
|
2001-09-13 08:31:21 +00:00
|
|
|
|
|
|
|
|
<p><h4>Notes</h4>
|
|
|
|
|
<p> At present, this task only supports the jasper compiler. In future,
|
2001-09-28 05:50:33 +00:00
|
|
|
other compilers will be supported by setting the <tt>jsp.compiler</tt> property.
|
2001-09-13 08:31:21 +00:00
|
|
|
<p> The jasper compiler option <code>-webapp</code> is not supported. Using
|
|
|
|
|
the <code>package</code> attribute it is possible to identify the resulting
|
|
|
|
|
java files and thus do full dependency checking - this task only rebuilds
|
|
|
|
|
java files if their jsp file has been modified.
|
|
|
|
|
|
|
|
|
|
<hr>
|
|
|
|
|
<p align="center">Copyright © 2000,2001 Apache Software Foundation. All rights
|
|
|
|
|
Reserved.</p>
|
|
|
|
|
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
|
|
|
|
|
