uCosminexus Application Server, Web Container Functionality Guide

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

2.3.1 Overview of JSP execution functionality

You can code JSP with the standard syntax that is the standard format of the JSP specifications and the XML syntax that is the format of the XML specifications. JSPs coded with the standard syntax are called the JSP pages and JSPs coded with the XML syntax are called the JSP documents. Hereafter, JSP pages and JSP documents are collectively referred to as a JSP file.

Organization of this subsection
(1) JSP configuration
(2) Translation errors

(1) JSP configuration

A JSP includes elements (directive, action, and scripting element) and template text. The template text includes white space. Normally, the white spaces included in the template text are maintained as are, but from the JSP 2.1 specifications, functionality is added to delete the unwanted white spaces included in the template text of tag files of the JSP pages or standard syntax. For details, see 6.2.7(2) Functionality for deleting unwanted white spaces.

Reference note
JSP EL has been provided from the JSP 2.0 specifications. JSP EL is a simplified language that allows you to code directly in an action or a template text. For details, see 2.3.3 Executing JSP EL.

(2) Translation errors

A translation error is an error that occurs when the JSP file cannot be converted to a Java file (JSP translation) due to syntax errors in the JSP compilation process.

JSP translation is executed at the following times, but translation errors might occur at these times:

When a translation error occurs during the JSP compilation on a J2EE server, the message KDJE39145-E is output in the servlet log and the message KDJE39186-E is output in the message log. When a translation error occurs during the processing of a request, the redirector returns the error status code 500.

If a translation error occurs during the JSP pre-compilation using the cjjspc command, the messages KDJE39145-E and KDJE39186-E are displayed on the console.

Note that translation errors might also occur due to other causes, such as analysis of the TLD file, JSP validation by the tag library validator, or the duplication of script variables specified in the TagExtraInfo class. In these cases, the messages are displayed according to the cause. The following table lists the messages displayed during the translation error, with their respective cause:

Table 2-7 Messages output when translation errors occur due to the causes other than the JSP compilation

Classification of causes Output messages
Parsing of the TLD file KDJE39214-E, KDJE39216-E, KDJE39193-E, KDJE39055-E, KDJE39205-E, KDJE39206-E, KDJE39207-E, KDJE39208-E, KDJE39296-E, KDJE39301-E, KDJE39302-E, KDJE39303-E, KDJE39305-E, KDJE39306-E, KDJE39307-E, KDJE39308-E
JSP validation by tag library validator KDJE39104-E, KDJE39105-E, KDJE39106-E, KDJE39107-E, KDJE39108-E, KDJE39115-E, KDJE39116-E, KDJE39117-E, KDJE39134-E, KDJE39135-E
Duplication of script variables specified in the TagExtraInfo class KDJE39131-E, KDJE39132-E, KDJE39133-E, KDJE39136-E, KDJE39282-E, KDJE39283-E, KDJE39291-E, KDJE39294-E