uCosminexus Application Server, Web Container Functionality Guide

[Contents][Glossary][Index][Back][Next]

2.4.4 Precautions for using the JSP debug functionality

This subsection describes the precautions for using the JSP debug functionality.

Organization of this subsection
(1) Deleting the class file created in the JSP debug functionality
(2) J2EE server settings when the cjjspc command is used to compile JSP

(1) Deleting the class file created in the JSP debug functionality

The class files created using the JSP debug functionality cannot be used in an environment where the JSP debug functionality is disabled. If you want to distribute the J2EE applications created in the JSP debug functionality-enabled environment to the JSP debug functionality-disabled environment, you must delete the class files created using the JSP debug functionality.

To delete class files:

  1. When the JSP pre-compilation functionality is used to compile JSP for applications in the exploded archive format
    Delete the JSP work directory of the JSP pre-compilation functionality. For details on the JSP working directory, see 2.5.5(2) Output destination of JSP compilation results.
  2. When JSP is compiled using any method other than the method of step 1.
    Use the cjstopapp command to stop the J2EE application.

(2) J2EE server settings when the cjjspc command is used to compile JSP

To use the cjjspc command for compiling JSPs, enable the JSP debug functionality in the J2EE server executed by JSPs.

If you specify the -debugging option for the cjjspc command to compile JSPs of the J2EE server applications in which the JSP debug functionality is disabled, the loaded class files will be different. Therefore, the Web container returns the error status code 404 for the HTTP request of JSP.