+

Search Tips   |   Advanced Search

Set JSP engine parameters


WAS does not support the modification of deployment descriptor extension parameters through the Administrative Console or through admin scripting.

To add, change or delete JSP engine configuration parameters...

 

  1. Open the WEB-INF/ibm-web-ext.xmi file.

    JSP engine configuration parameters are stored in a web module's configuration directory or in a web modules's binaries directory in the WEB-INF/ibm-web-ext.xmi file. Open the WEB-INF/ibm-web-ext.xmi file from:

    • The configuration directory, as in the following example: {WAS_ROOT}/profiles/profilename/config/cells/cellname/applications/enterpriseappname/ deployments/deployedname/webmodulename

    • The binaries directory if an application was deployed into WAS with the flag "Use Binary Configuration" set to true. An example of a binaries directory is: {WAS_ROOT}/profiles/profilename/installedApps/nodename/EnterpriseAppName/WebModuleName/

  2. Edit the WEB-INF/ibm-web-ext.xmi file.

    • To add configuration parameters, use the following format: xmi:id="JSPAttribute_6" name="parametername" value="parametervalue"/>

    • To delete configuration parameters, either delete the line from the file, or enclose the statement with <!-- --> tags.

  3. Save the file.

  4. Restart the Enterprise Application. It is not necessary to restart the server for parameter changes to take effect. However, some JSP engine configuration parameters affect the Java source code that is generated for a JSP. If such a parameter is changed, then retranslate the JSPs in the Web module to regenerate Java source. Use the batch compiler to retranslate all JSPs in a Web module. The batch compiler uses the JSP engine configuration parameters that we have set in the ibm-web-ext.xmi file, unless you specifically override them. The topic JSP engine configuration parameters" identifies the parameters that affect the generated Java source.

 

Example

The following is a sample of the WEB-INF/ibm-web-ext.xmi file. The lines in bold text are JSP engine configuration parameters. 

<?xml version="1.0" encoding="UTF-8"?>
<webappext:WebAppExtension xmi:version="2.0" 
    xmlns:xmi=http://www.omg.org/XMI
   
    xmlns:webappext="webappext.xmi" 
    xmlns:webapplication="webapplication.xmi" xmi:id="WebAppExtension_1"   
   reloadInterval="9" reloadingEnabled="true" defaultErrorPage="error.jsp" additionalClassPath="" 
   fileServingEnabled="true" directoryBrowsingEnabled="false" serveServletsByClassnameEnabled="true" 
   autoRequestEncoding="true" autoResponseEncoding="false"
   <webApp href="WEB-INF/web.xml#WebApp_1"/>
   <jspAttributes xmi:id="JSPAttribute_1" name="useThreadTagPool" value="true"/>
   <jspAttributes xmi:id="JSPAttribute_2" name="verbose" value="false"/>
   <jspAttributes xmi:id="JSPAttribute_3" name="deprecation" value="false"/>
   <jspAttributes xmi:id="JSPAttribute_4" name="reloadEnabled" value="true"/>
   <jspAttributes xmi:id="JSPAttribute_5" name="reloadInterval" value="5"/>
   <jspAttributes xmi:id="JSPAttribute_6" name="keepgenerated" value="true"/>
   <!--<jspAttributes xmi:id="JSPAttribute_7" name="trackDependencies" value="true"/> -->
   
</webappext:WebAppExtension>

The integer n in JSPattribute_n has to be unique within the file.


JSP engine
JSP engine configuration parameters
JSPs troubleshooting tips

 

Related concepts


JSPs
Global tag libraries (deprecated)

 

Related


dbmodify tag JSPs syntax (deprecated)
JSPBatchCompiler
Web apps: Links