The following figure shows the flow of usage procedure of the JSP debug functionality when compiling JSP with the J2EE server:

Figure 2-2 Usage procedure of the JSP debug functionality (when compiling JSP with the J2EE server)

The following points describe the procedure in the above figure:

1. Setting up the J2EE server
   Enable the JSP debug functionality. Also, enable JSP reload. For details on JSP reload, see 13.8.9 Reloading JSP in the uCosminexus Application Server Common Container Functionality Guide.
   
2. Starting the J2EE server
   Start the J2EE server.
   If the JSP debug functionality is enabled, the KDJE39322-W message is output in the message log when the J2EE server starts.
   
3. Creating or modifying the JSP file
   Create or modify JSP files.
   
4. Testing and debugging the JSP file
   Use the debug tool supporting JPDA, such as WTP to test and debug. To modify JSPs, return to step 3.
   
5. Distribution of JSP to the execution environment
   Export the J2EE applications containing the created JSPs in the development environment, and then import the applications into the execution environment.
   

For compiling all JSPs before starting the J2EE applications, execute the JSP pre-compilation functionality with the cjjspc command. For details on the JSP pre-compilation functionality, see 2.5 JSP pre-compilation functionality and maintaining compilation results.

The following figure shows the flow of usage procedure of the JSP debug functionality when JSP pre-compilation is executed with the cjjspc command.

Figure 2-3 Usage procedure of the JSP debug functionality (when compiling JSP with the cjjspc command)

The following points describe the procedure in the above figure:

1. Starting the J2EE server
   Enable the JSP debug functionality. Also, enable JSP reload. For details on JSP reload, see 13.8.9 Reloading JSP in the uCosminexus Application Server Common Container Functionality Guide.
   If the JSP debug functionality is enabled, the KDJE39322-W message is output in the message log when the J2EE server starts.
   
2. Creating or modifying the JSP file
   Create or modify JSP files.
   
3. Executing the JSP pre-compile
   Use the cjjspc command to execute the JSP pre-compilation functionality. Specify the -debugging option to execute the command, and compile the JSP file.
   During the execution of the cjjspc command, the KDJE53442-W message is output in the console log.
   
4. Testing and debugging JSP
   Use the debug tool supporting JPDA, such as WTP for testing and debugging. To modify JSPs, return to step 2.
   
5. Re-compiling JSP
   Delete the JSP work directory. Also, use the cjjspc command without specifying the -debugging option to re-compile the JSP file.
   Note that if the JSP file is not re-compiled, you cannot execute JSP. For details, see 2.4.4 Precautions for using the JSP debug functionality.
   
6. Distribution of JSP to the execution environment
   Export the J2EE applications containing the created JSP in the development environment, and then import the applications into the execution environment.
   

For details on the cjjspc command, see cjjspc (JSP pre-compilation) in the uCosminexus Application Server Command Reference Guide.