Web module deployment settings
Configure an instance of web module deployment.
From the admin console, click...
Applications > Application Types > WebSphere enterprise applications > application_name > Manage Modules > Web_module_instance.
URI
Relative location of the module within the application enterprise archive (EAR) file.
Alternate deployment descriptor
Alternate deployment descriptor for the module as defined in the application deployment descriptor according to the Java EE specification.
Starting weight
Order that modules are started. Lower-weighted modules are started before higher weighted modules.
If the application deployment descriptor specifies the <initialize-in-order>true</initialize-in-order> element, the default starting weights reflect the order specified in the deployment descriptor. Otherwise, the defaults are determined based on module type (RAR modules start before EJB modules, which start before web modules).
Class loader order
Specifies 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 product class loaders is Classes loaded with parent class loader first. By specifying Classes loaded with application class loader first, 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.
Information Value Data type String Default Classes loaded with parent class loader first
Related:
Web modules Class loaders Configure web module class loaders Modify the default web container configuration Web applications: Resources for learning