JavaServer Pages attribute assembly settings
Use the JavaServer Pages (JSP) attributes page to set JSP attributes that are used by servlets that implement JSP processing behavior.
Access this page by traversing the following path in the Application Assembly Tool:
Web Modules > component_instance > Assembly Property Extensions
- JSP Attribute (Name)
- Specifies the name of an attribute.
Data type String - JSP Attribute (Value)
- Specifies the value of an attribute.
Data type String The WebSphere JSP container supports the following JSP attributes:
- classdebuginfo
- Indicates the compiler should include debugging information in the generated classfile.
classdebuginfo true or false Default is false.
- classpath
- Specifies an additional classpath for compiling the generated servlets.
classpath classpath or null Default is null.
- deprecation
- Indicates the compiler should generate deprecation warnings when compiling the generated Java source.
deprecation true or false Default is false.
- ieClassID
- Indicates the Java plugin COM class ID for Internet Explorer. The <jsp:plugin> tags use this value.
ieClassID classid Default is clsid:8AD9C840-044E-11D1-B3E9-00805F499D93.
- javaEncoding
- Indicates the Java platform encoding to use to generate the JSP page servlet.
javaEncoding encoding value Default is UTF-8.
- jspCompilerPath
- Indicates the path of the compiler to use for compiling JSP pages.
jspCompilerPath path name or null Default is null.
- keepgenerated
- Indicates the Java files generated by the JSP compiler during the translation phase of the processing should be kept.
keepgenerated true or false Default is false.
- largefile
- Specifies support for large files. When the Java code is generated, the HTML data in a JSP file is stored separately instead of being saved as constant string data in the generated servlet.
largefile true or false Default is false.
- mappedfile
- Indicates the compiler should generate Java source that includes a print statement for every line in the JSP file. Use this option for debugging purposes only. It is not recommended for production environments because the mappedfile option generates too many out.print() statements.
mappedfile true or false Default is false.
- scratchdir
- Specifies the directory where the generated classfiles are created.
scratchdir directory name. Default is [WAS_INSTALL_ROOT]/temp.
Note: The system property com.ibm.websphere.servlet.temp.dir can be used to set the scratchdir option on a server-wide basis. This setting, if it is present, overrides the system property.
- usePageTagPool
- Enables or disables the reuse of custom tag handlers on an individual JavaServer Page basis.
usePageTagPool true or false Default is false.
The note in the useThreadTagPool attribute description also applies to theusePageTagPool attribute.
- useThreadTagPool
- Enables or disables the reuse of custom tag handlers on a per request thread basis.
useThreadTagPool true or false Default is false.
The note in the useThreadTagPool attribute description also applies to theusePageTagPool attribute.
Note: Enabling custom tag handler reuse might reveal problems in your tag handler code regarding the tags ability to be reused. A custom tag handler should always do two things:
- The release() method of the tag handler should reset its state and release any private resources that it might have used. The JSP engine guarantees the release() method will be called before the tag handler is garbage collected.
- In the doEndTag() method, all instance states associated with this instance must be reset.
- verbose
- Indicates the compiler should generate verbose output when compiling the generated Java source code.
verbose true or false Default is false.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.