Class loader settings

Use this page to configure a class loader for applications that reside on an appserver.

To view this console page, click Servers > Application servers > server > Java and Process Management > Class loader > class_loader_ID.

 

Configuration tab

Class loader ID

Provides a string that is unique to the server identifying the class-loader instance. WAS assigns the identifier.

Data type

String

Class loader order

Specify 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 WAS class loaders is Classes loaded with parent class loader first. By specifying Classes loaded with application class loader first, your application can override classes contained in the parent class loader, but this action can potentially result in ClassCastException or LinkageErrors if you have mixed use of overridden classes and non-overridden classes.

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

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

Data type	String
Default	Classes loaded with parent class loader first

---

 

Related tasks

Class loading

 

Related Reference

Library reference collection

 

Reference topic