mirror of
https://github.com/apache/ant.git
synced 2025-05-18 22:14:47 +00:00
85 lines
2.4 KiB
HTML
85 lines
2.4 KiB
HTML
|
<html>
|
||
|
|
<head><title> Ant optional task manual : wljspc </title></head>
|
||
|
|
<body>
|
||
|
|
<h1>wljspc</h1>
|
||
|
|
<h3>Description</h3>
|
||
|
|
<p>Class to precompile JSP's using weblogic's jsp compiler (weblogic.jspc)</p>
|
||
|
|
Tested only on Weblogic 4.5.1 - NT4.0 and Solaris 5.7,5.8<br>
|
||
|
|
<h3>Parameters</h3>
|
||
|
|
<table border="1" cellPadding="2" cellSpacing="0">
|
||
|
|
<tbody>
|
||
|
|
<tr>
|
||
|
|
<th>Attribute</th>
|
||
|
|
<th>Values</th>
|
||
|
|
<th>Required</th>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>src</td>
|
||
|
|
<td>oot of source tree for JSP, ie, the document root for your weblogic server</td>
|
||
|
|
<td>Yes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>
|
||
|
|
dest</td>
|
||
|
|
<td> root of destination directory, what you have set as WorkingDir in the weblogic properties</td>
|
||
|
|
<td>Yes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>
|
||
|
|
package</td>
|
||
|
|
<td> start package name under which your JSP's would be compiled</td>
|
||
|
|
<td>Yes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>
|
||
|
|
classpath</td>
|
||
|
|
<td>Class path to use when compiling jsp's</td>
|
||
|
|
<td>Yes</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
<p>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
A classpath should be set which contains the weblogic classes as well as all application classes<br>
|
||
|
|
referenced by the JSP. The system classpath is also appended when the jspc is called, so you may<br>
|
||
|
|
choose to put everything in the classpath while calling Ant. However, since presumably the JSP's will reference<br>
|
||
|
|
classes being build by Ant, it would be better to explicitly add the classpath in the task<br>
|
||
|
|
<br>
|
||
|
|
The task checks timestamps on the JSP's and the generated classes, and compiles<br>
|
||
|
|
only those files that have changed.<br>
|
||
|
|
<br>
|
||
|
|
It follows the weblogic naming convention of putting classes in<br>
|
||
|
|
<b> _dirName/_fileName.class for dirname/fileName.jsp </b><br>
|
||
|
|
<br>
|
||
|
|
</p>
|
||
|
|
<h3><br>
|
||
|
|
Example<br>
|
||
|
|
</h3>
|
||
|
|
<p>
|
||
|
|
<target name="jspcompile" depends="compile"><br>
|
||
|
|
<wljspc src="c:\\weblogic\\myserver\\public_html" dest="c:\\weblogic\\myserver\\serverclasses" package="myapp.jsp" ><br>
|
||
|
|
<classpath><br>
|
||
|
|
<pathelement location="${weblogic.classpath}" /><br>
|
||
|
|
<pathelement path="${compile.dest}" /><br>
|
||
|
|
</classpath><br>
|
||
|
|
<br>
|
||
|
|
</wljspc><br>
|
||
|
|
</target>
|
||
|
|
</p>
|
||
|
|
<h3>
|
||
|
|
<br>
|
||
|
|
Limitations
|
||
|
|
</h3>
|
||
|
|
<p>
|
||
|
|
This works only on weblogic 4.5.1
|
||
|
|
<br>
|
||
|
|
It compiles the files thru the Classic compiler only.<br>
|
||
|
|
Since it is my experience that weblogic jspc throws out of memory error on being given too<br>
|
||
|
|
many files at one go, it is called multiple times with one jsp file each.
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|