stevel 01/10/18 17:34:05
Modified: docs/manual/OptionalTasks jspc.html
Log:
documented uriroot and uribase options; cleaned up some other bits based on
more experience with the task.
Revision Changes Path
1.3 +44 -11 jakarta-ant/docs/manual/OptionalTasks/jspc.html
Index: jspc.html
===================================================================
RCS file: /home/cvs/jakarta-ant/docs/manual/OptionalTasks/jspc.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jspc.html 2001/09/28 05:50:33 1.2
+++ jspc.html 2001/10/19 00:34:05 1.3
@@ -10,10 +10,10 @@
<h2><a name="jspc">jspc</a></h2>
<h3>Description</h3>
-<p> Ant task to run the jsp compiler.
+<p> Ant task to run the JSP compiler and turn JSP pages into Java source.
<p>
-It can be used to precompile jsp pages for fast initial invocation
+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.
@@ -72,8 +72,7 @@
</tr>
<tr>
<td valign="top">classpath</td>
- <td valign="top">The classpath to use to run the jsp compiler,
- and bring in any tag libraries.
+ <td valign="top">The classpath to use to run the jsp compiler.
This can also be specified
by the nested element <code>classpath</code>
<a href="../using.html#path">Path</a>).</td>
@@ -90,6 +89,24 @@
<td valign="top">flag to control action on compile failures:
default=yes</td>
<td valign="top" align="center">No</td>
</tr>
+ <tr>
+ <td valign="top">uribase</td>
+ <td valign="top">
+ The uri context of relative URI
+ references in the JSP pages. If it does not
+ exist then it is derived from the location of the file
+ relative to the declared or derived value of <tt>uriroot.</tt>
+ </td>
+ <td valign="top" align="center">No</td>
+ </tr>
+ <tr>
+ <td valign="top">uriroot</td>
+ <td valign="top">
+ The root directory that uri files should be resolved
+ against.
+ </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
@@ -103,6 +120,22 @@
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>
+<P><tt>uriroot</tt> specifies the root of the web
+application. This is where all absolute uris will be resolved from.
+If it is not specified then the first JSP page will be used to derive
+it. To derive it each parent directory of the first JSP page is
+searched for a <tt>WEB-INF</tt> directory, and the directory closest to
+the JSP page that has one will be used. If none can be found then the
+directory Jasperc was called from will be used. This only affects pages
+translated from an explicitly declared JSP file -including references
+to taglibs</P>
+
+<P><tt>uribase</tt> is used to establish the uri context of
+relative URI references in the JSP pages. If it does not exist then it
+is derived from the location of the file relative to the declared or
+derived value of <tt>uriroot</tt>. This only affects pages
+translated from an explicitly declared JSP file.</P>
+
<h3>Parameters specified as nested elements</h3>
This task is a <a href="../dirtasks.html">directory based task</a>, like
@@ -116,10 +149,8 @@
<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.
+The classpath used to compile the JSP pages, specified as for any other
+classpath.
<h4>classpathref</h4>
a reference to an existing classpath
@@ -140,7 +171,6 @@
<jspc
destdir="interim"
verbose="1">
- classpath="lib/taglibs.jar"
srcdir="src"
package="com.i3sp.jsp"
<include name="**/*.jsp" />
@@ -157,8 +187,8 @@
debug="on" />
</pre>
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
+bytecodes. Include lib/taglib jar in the java compilation.
+ Dependency checking is used to scrub the
java files if class dependencies indicate it is needed.
<p><h4>Notes</h4>
@@ -168,6 +198,9 @@
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.
+<p>
+Jasper generates JSP pages against the JSP1.3 specification -an
implementation of
+version 2.2 of the servlet specification is needed to compile or run the
java code.
<hr>
<p align="center">Copyright © 2000,2001 Apache Software Foundation. All
rights
