The ant task JspC exposes all the batch compiler configuration options. It executes the batch compiler under the covers. It is backward compatible with the WebSphere Application Server 5.x version of the JspC ant task. The following table lists all the ant task attribute and their batch compiler equivalents.
JspC attribute | Equivalent batch complier parameter |
earPath | -ear.path |
warPath | -war.path |
src
Same as warPath, for backward compatiblity | -war.path |
enterpriseAppName | -enterpriseapp.name |
responseFile | -response.file |
webmoduleName | -webmodule.name |
fileName | -filename -config.root |
configRoot | -config.root |
cellName | -cell.name |
nodeName | -node.name |
serverName | -server.name |
profileName | -profileName |
extractToDir | -extractToDir |
compileToDir
same as compileToDir, for backward compatibility | -compileToDir -compileToDir |
compileToWebInf | -compileToWebInf |
jspCompileClasspath | -jspCompileClasspath |
compilerOptions | -compilerOptions |
recurse | -recurse |
removeTempDir | -removeTempDir |
translate | -translate |
compile | -compile |
forceCompilation | -forceCompilation |
useFullPackageNames | -useFullPackageNames |
trackDependencies | -trackDependencies |
createDebugClassfiles | -createDebugClassfiles |
keepgenerated | -keepgenerated |
keepGeneratedclassfiles | -keepGeneratedclassfiles |
usePageTagPool | -usePageTagPool |
useThreadTagPool | -useThreadTagPool |
classloaderParentFirst | -classloader.parentFirst |
classloaderSingleWarClassloader | -classloader.singleWarClassloader |
additionalClasspath | -additional.classpath |
classpath
same as additionalClasspath, for backward compatibility | -additional.classpath |
verbose | -verbose |
deprecation | -deprecation |
javaEncoding | -javaEncoding |
compileWithAssert | -compileWithAssert |
useJikes | -useJikes |
jspFileExtensions | -jsp.file.extensions |
logLevel | -log.level |
wasHome | none |
Classpathref | none |
Below is an example of a build script with multiple targets, each with different attributes. The following commands are used to execute the script: On Windows:
ws_ant -Dwas.home=%WAS_HOME% -Dear.path=%EAR_PATH% -Dextract.dir=%EXTRACT_DIR%On Unix or i5/OS:
ws_ant jspc2 -Dwas.home=%WAS_HOME% -Dapp.name=%APP_NAME% -Dwebmodule.name=%MOD_NAME%
ws_ant jspc3 -Dwas.home=%WAS_HOME% -Dapp.name=%APP_NAME% -Dwebmodule.name=%MOD_NAME% -Ddir.name=%DIR_NAME%
ws_ant -Dwas.home=$WAS_HOME -Dear.path=$EAR_PATH -Dextract.dir=$EXTRACT_DIRExample build.xml Using the JspC Task
ws_ant jspc2 -Dwas.home=$WAS_HOME -Dapp.name=$APP_NAME -Dwebmodule.name=$MOD_NAME
ws_ant jspc3 -Dwas.home=$WAS_HOME -Dapp.name=$APP_NAME -Dwebmodule.name=$MOD_NAME -Ddir.name=$DIR_NAME
<project name="JSP Precompile" default="jspc1" basedir="."> <taskdef name="wsjspc" classname="com.ibm.websphere.ant.tasks.JspC"/> <target name="jspc1" description="example using a path to an EAR, and extracting the EAR to a directory"> <wsjspc wasHome="${was.home}" earpath="${ear.path}" forcecompilation="true" extractToDir="${extract.dir}" useThreadTagPool="true" keepgenerated="true" jspCompileClasspath="" /> </target> <target name="jspc2" description="example using an enterprise app and webmodule"> <wsjspc wasHome="${was.home}" enterpriseAppName="${app.name}" webmoduleName="${webmodule.name}" removeTempDir="true" forcecompilation="true" keepgenerated="true" jspCompileClasspath="" /> </target> <target name="jspc3" description="example using an enterprise app, webmodule and specific directory"> <wsjspc wasHome="${was.home}" enterpriseAppName="${app.name}" webmoduleName="${webmodule.name}" fileName="${dir.name}" recurse="false" forcecompilation="true" keepgenerated="true" jspCompileClasspath="" /> </target> </project>
Related concepts
JavaServer Pages
Related reference
JSP batch compiler tool