TechNote (Archived)

JRun 3.1: Documentation discrepancy concerning JSPC

Macromedia has identified three documentation inaccuracies concerning the JSPC off-line compiler for JRun 3.1. In each case, actual behavior is slightly different from the documented description.

1. The JRun 3.1 documentation for JSPC displays a usage of:
   
   java [-classpath classpath] JSPC [-compiler "compiler_spec"] JSP_path
   
   to specify the compiler to be used for the off-line JSP compilation operation. However, using the -compiler switch results in the following exception:
   

    java.io.IOException: CreateProcess: ompiler error=2 java.io.IOException: CreateProcess: ompiler error=2       at java.lang.Win32Process.create(Native Method)       at java.lang.Win32Process.<init>(Win32Process.java:61) 

   
   The correct switch to pass to JSPC is either -c or--compiler, as displayed when invoking the JSPC-help command line option. Either of these options allows you to select the compiler without throwing errors.
2. The JSPC documentation also states:
   
   compiler - (Optional) Specifies a quoted string containing the compiler and compiler settings to use for the compile. If you omit this parameter, JRun compiles JSPs in-process using the Sun javac compiler.
   
   However, if you omit the -c parameter and add the-g (debug) parameter, you will notice that the setting for "jsp.jikes.compiler" in the global.properties file will actually take effect, rather than defaulting to "javac". This only happens when using the -g command option.
3. Compiling a JSP with the -g parameter also generates an additional XML file. This is not explicitly documented, but this is correct behavior. The -g parameter may be used to provide additional debugging information.
   
   During the compilation process, JRun creates an interim XML file that may be saved and examined by specifying the -g switch.

Search Support

---