You can define the class loader policy for a specific application
for a WebSphere® Application
Server v6.0 remote or local server.
Prerequisites
- Create an enterprise application and target the server to WebSphere Application
Server v6.0.
To set class loader policy for an application on a WebSphere Server
v6.0, follow these steps:
- Switch to the J2EE perspective.
- In the Project Explorer view, expand the Enterprise
Applications folder.
- Under the enterprise application project folder for which you want
to set class loader policy, double-click the Deployment Descriptor to
open the Application Deployment Descriptor editor.
- Select the Deployment tab at the bottom
of the editor.
- Expand the Application section.
- In the Applications list box, select the application to modify
the class loader settings.
- In the Classloader mode field, select the
class loading mode for the application:
- PARENT_FIRST causes the class loader to
delegate the loading of classes to its parent class loader before attempting
to load the class from its local class path.
- PARENT_LAST causes the class loader to
attempt to load classes from its local class path before delegating the class
loading to its parent.
- In the WAR classloader policy field, select
the isolation level of Web modules.
- If this policy is set to APPLICATION, then
the Web project contents also are loaded by the application class loader (in
addition to the EJB files, RAR files, dependency JAR files, and shared libraries).
- If the policy is set to MODULE, then each Web
project receives its own class loader whose parent is the application class
loader.
- In the Start weight field, specify the order
in which projects in an J2EE application are started. Lower weighted projects
are started before higher weighted projects.
- Save your changes and close the editor. The class loader
policy settings have been added to the deployment descriptor files.