This rule flags the <is-xml> and <page-encoding> JSP configuration options found in the <jsp-property-group> of the web.xml file.
jsp-config-property example:The JSP specification was clarified with respect to how these configuration options apply to included JSP files. Starting in WebSphere Application Server V8, the <is-xml> and <page-encoding> configuration options only apply to those JSP files which match the URL pattern and not to included JSP files unless they also match the URL pattern.
In previous releases, if a JSP was included (such as a prelude or coda) by another JSP that matched a property-group, then the original property-group settings applied to the included file as well. Most properties defined in a JSP property group apply to an entire translation unit. That is, the requested JSP file that is matched by its URL pattern and all the files it includes via the include directive. The exceptions are the <page-encoding> and the <is-xml> properties, which apply separately to each JSP file matched by its URL pattern.
The configuration option is flagged so that you can either fix the configuration or revert back to previous behavior. To fix the problem, create another <jsp-property-group> to match the included files where you want the configuration applied.
Example fix:The web container custom property com.ibm.wsspi.jsp.reusepropertygroupconfigoninclude or the JSP attribute reusePropertyGroupConfigOnInclude can be used to revert back to the old behavior. Set either to true to revert the behavior. The default for this property is false which allows for the new specification-defined behavior.
For additional information see: