Web module deployment settings
Use this page to configure an instance of Web module deployment.
To view this console page, click Applications > Enterprise Application > application_instance > Manage Modules > Web_module_instance.
- URI
- Relative location of the module within the application EAR.
- Alternate deployment descriptor
Specify the alternate deployment descriptor for the module as defined in the application deployment descriptor according to the J2EE specification.
- Start weight
Specify the order in which modules are started. Lower weighted modules are started before higher weighted modules.
- 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 product 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.
Data type String Default Classes loaded with parent class loader first
Related concepts
Web modules
Class loaders
Related tasks
Configure Web module class loaders
Modifying the default Web container configuration
Related Reference
Web applications: Resources for learning
Reference topic