This rule flags the deprecated reloadInterval
and reloadingEnabled attributes of the IBM deployment descriptor extensions.
These attributes can be defined on both the WAR file extension (WEB-INF/ibm-web-ext.xmi)
and the application extension (META-INF/ibm-application-ext.xmi).
Instead of using the deprecated attributes, alternative settings are available.
For JSP reloading, use the reloadEnabled and reloadInterval
JSP engine parameter in the WEB-INF/ibm-web-ext.xmi or
WEB-INF/ibm-web-ext.xml files.
For EJB and web module class reloading, use the reload enable and interval options
provided during application deployment.
For example, the following example highlights the deprecated
reloadInterval and reloadingEnabled
attributes in a WAR extension file. The example also shows the jspAttributes
setting that supersedes the deprecated settings. In this example, the JSP file reload interval
would be 10 instead of 3.
Class reloading for EJB and web modules is controlled by the reload enable and interval options provided during application deployment and saved in the deployment.xml file. These deployment options can also be changed by editing the application from the administrative console. Click Applications > Application Types > WebSphere enterprise applications > application_name > Class loading and update detection.
After adding jspAttributes for JSP file reloading or setting the deployment options, you can
remove the deprecated reloadInterval and reloadingEnabled attributes.
The following resources are available to assist in setting reload attributes:
The Deprecated features list is in the documentation.
If View Results does not properly highlight the reload attribute in the *-ext.xmi file, you might need to associate the .xmi file extension to the XML editor in Eclipse. Click Window > Preferences > General > Editors > File Associations. Add .xmi to the list in the top half of the panel. In the bottom half of the panel, select XML Editor and click Default.