The JSPCommand- Line Compiler You can precompile JSPs for faster performance; this is recommended for production servers. Acommand- line JSP compiler is included with iPlanet Web Server. The JSP compiler is located underserver_root/bin/https/ bin( make sure this directory is in your path). TheIWS_SERVER_ HOME environment variable must be set to theserver_ root directory. The format of the jspc command is as follows: jspc[ options]jsp_ files Thejsp_ files can be one of the following: The options for the jspc command are: files One or more JSP files to be compiled.- webapp dir A directory containing a web application. All JSPs in the directory and its subdirectories are compiled. You cannot specify a WAR, JAR, or ZIP file.- q Enables quiet mode( same as- v0). Only fatal error messages aredisplayed.
-v[ level] Enables verbose mode. The level is optional; the default is 2. Possible level values are: • 0 - fatal error messages only • 1 - error messages only • 2 - error and warning messages only • 3 - error, warning, and informational messages • 4 - error, warning, informational, and debugging messages- d dir Specifies the output directory for the compiled JSPs. Package directories are automatically generated based on the directories containing the uncompiled JSPs. The defaulttop- level directory is the directory from which jspc is invoked.- dd dir Specifies the literal output directory for the compiled JSPs. Package directories are not made. The default is the directory from which jspc is invoked.- p name Specifies the name of the target package for all specified JSPs, overriding the default package generation performed by the- d option.- c name Specifies the target class name of the first JSP compiled. Subsequent JSPs are unaffected.- mapped Generates separate write calls for each HTML line and comments that describe the location of each line in the JSP file. By default, all adjacent write calls are combined and no location comments are generated.-die[ code] Causes the JVM to exit and generates an error return code if a fatal error occurs. If the code is absent or unparsable it defaults to 1.- uribase dir Specifies the URI directory to which compilations are relative. Applies only to explicitly declared JSP files. This is the location of each JSP file relative to the uriroot. If this cannot be determined, the default is/.
- uriroot dir Specifies the root directory against which URI files are resolved. Applies only to explicitly declared JSP files. If this option is not specified, all parent directories of the first JSP page are searched for aWEB- INF subdirectory. The closest directory to the JSP page that has one is used. If none of the JSP’s parent directories have aWEB- INF subdirectory, the directory from which jspc is invoked is used.- webinc file Creates partial servlet mappings for the- webapp option, which can be pasted into aweb. xml file.- webxml file Creates an entireweb. xml file for the- webapp option.- iepluginclass_ id Specifies the Java plugin COM class ID for Internet Explorer. Used by the<jsp: plugin> tags.- genclass Generates class files in addition to Java files. The JDKtools. jar file must be in the JVMclasspath.
The- webinc and- webxml options may not be useful for JSPs in iPlanet Web Server. For example, this command( all on one line) compiles the JSPs in the HelloWorld web application: jspc- d dir- genclass- webappserver_root/plugins/servlets/examples/web-apps/ HelloWorld The compiled JSPs are written underdir/_ jsps/. You can then put these class files in a. JAR file. Additional documentation for the JSP compiler is on the Jakarta site:http://jakarta.apache. org/ Jasper and iPlanet Web Server 6.0 are not tightly integrated, so you might need to edit the JVM Classpath( in the Configure JVM Attributes page of the Server Manager or in thejvm12. conf file) when deploying JSPs using tag libraries, beans, and so on. For more information about JVM settings, see Appendix C,“ JVM Configuration.”