WAS v8.5 > Reference > Sets

Class loading and update detection settings page

Use this page to configure use of class loaders by an application.

To view this dmgr console page, click Applications > Application Types > WebSphere enterprise applications > application_name > Class loading and update detection.

If an application is running, changing an application setting causes the application to restart. On stand-alone servers, the application restarts after you save the change. On multiple-server products, the application restarts after you save the change and files synchronize on the node where the application is installed. To control when synchronization occurs on multiple-server products, deselect Synchronize changes with nodes on the Console preferences page.

For IBM extension and binding files, the .xmi or .xml file name extension is different depending on whether you are using a pre-Java EE 5 application or module or a Java EE 5 or later application or module. An IBM extension or binding file is named ibm-*-ext.xmi or ibm-*-bnd.xmi where * is the type of extension or binding file such as app, application, ejb-jar, or web. The following conditions apply:

• For apps and modules that use a Java EE version prior to version 5, the file extension must be .xmi.

• For apps and modules that use Java EE 5 or later, the file extension must be .xml. If .xmi files are included with the application or module, the product ignores the .xmi files.

However, a Java EE 5 or later module can exist within an application that includes pre-Java EE 5 files and uses the .xmi file name extension.

The ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, and ibm-portlet-ext.xmi files continue to use the .xmi file extensions. sptcfg

Override class reloading settings for web and EJB modules

Whether to enable class reloading when application files are updated.

Select Override class reloading settings for web and EJB modules to set reloadEnabled to true in the deployment.xml file for the application. If an application's class definition changes, the application server run time stops and starts the application to reload application classes.

Reloading settings in the deployment.xml file override the reloading settings for all web and EJB modules that can be defined in ibm-web-ext.xmi and META-INF/ibm-application-ext.xmi files. The following table shows the reload settings in the deployment.xml file based on the setting of reloadEnabled.

JSP and servlet class reloading. The following table shows the reload settings in the deployment.xml file based on the setting of reloadEnabled.

deployment.xml	ibm-web-ext.xmi	ibm-web-ext.xmi (reloadingEnabled)	ibm-web-ext.xmi (jspAttributes name="reloadEnabled"	Change in JSP	Change in servlet class
reloadEnabled = false	reloadInterval set or not	true	true	Translate, recompile, reload	loading new class
relaodEnalbed = false		false	true	Translate, recompile, reload	NO loading of new class
reloadEnalbed = false		true	false	NO translate, recompile, reload	Loading new class
reloadEnalbed = true	reloadInterval > 0	false or true	false	NO translation or reload of JSP	Loading new class at specified interval
reloadEnabled = true		false or true	true	Translation and reload JSP	Loading new class
reloadEnabled = true	reloadInterval = 0	false or true	false	NO translation or reload of JSP	NO loading of new class
reloadEnabled = true	reloadInterval = 0	false or true	true	Translation and reload of JSP	NO loading of new class
reloadEnabled = false in the deployment.xml file means the properties in the ibm-web-ext.xmi file will be in effect.( whatever is set for reloadingEnabled in the ibm-web-ext.xmi file. reloadEnabled = true in the deployment.xml AND reloadInterval = value of polling interval set to a value greater than 0 using the dmgr console, causes reloading in time interval specified by reloadInterval. reloadEnabled = true in the deployment.xml AND reloadInterval= 0 causes no class reloading. To ensure the reloading of any servlet class is disabled no matter what is set in the ibm-web-ext.xmi file, then make sure the reloadInterval in the ibm-web.ext.xmi file is set to 0. If jspAttributes name="reloadEnabled" is NOT present in the ibm-web-ext.xmi file, then the reloadingEnabled value becomes the operative reload action.

Information	Value
Data type	Boolean
Default	false

Polling interval for updated files

Number of seconds to scan the application's file system for updated files. The default is the value of the reloading interval attribute in the IBM extension (META-INF/ibm-application-ext.xmi) file of the EAR file.

This Polling interval for updated files setting is the same as the Reload interval in seconds field on the application installation and update wizards.

To enable reloading, specify a value greater than zero (for example, 1 to 2147483647). To disable reloading, specify zero (0). The range is from 0 to 2147483647.

The reloading interval attribute takes effect only if class reloading is enabled.

Information	Value
Data type	Long
Units	Seconds
Default	3

Class loader order

Whether the class loader searches in the parent class loader or in the application class loader first to load a class. The standard for development kit class loaders and WebSphere Application Server class loaders is Classes loaded with parent class loader first. By specifying Classes loaded with local class loader first (parent last), the application can override classes contained in the parent class loader, but this action can potentially result in ClassCastException or LinkageErrors if we have mixed use of overridden classes and non-overridden classes.

The options are Classes loaded with parent class loader first and Classes loaded with local class loader first (parent last). The default is to search in the parent class loader before searching in the application class loader to load a class.

For the application to use the default configuration of Jakarta Commons Logging in WAS, set this application class loader mode to Classes loaded with parent class loader first. For the application to override the default configuration of Jakarta Commons Logging in WAS, the application must provide the configuration in a form supported by Jakarta Commons Logging and this class loader mode must be set to Classes loaded with local class loader first (parent last). Also, to override the default configuration, set the class loader mode for each web module in the application so the correct logger factory loads.

Information	Value
Data type	String
Default	Classes loaded with parent class loader first

WAR class loader policy

Whether to use a single class loader to load all WAR files of the application or to use a different class loader for each WAR file.

The options are Class loader for each WAR file in application and Single class loader for application. The default is to use a separate class loader to load each WAR file.

Information	Value
Data type	String
Default	Class loader for each WAR file in application

Related concepts:

Class loaders

Related

Configure the use of class loaders by an application
Configure enterprise application files
Class loading

Reference:

Enterprise application settings
Class loader page
JSP and JSF option settings
Application server settings

+

Search Tips   |   Advanced Search