The Class loader configuration used for reloading differs according to the scope of local call optimization. The following table describes the mapping of the scope of local call optimization and the class loader configuration. For details on the class loader configuration, see Appendix B Class loader configuration.
Table 13-11 Mapping of the scope of local call optimization and class loader configuration
Items | Value of the ejbserver.rmi.localinvocation.scope key # | ||
---|---|---|---|
all | app | none | |
Scope of local call optimization | Within the same J2EE server. | Within the same application. | There is no range. |
Class loader configuration | Class loader configuration used for local call optimization. | Default class loader configuration. | Default class loader configuration. |
#: This key is specified in usrconf.properties.
With the reload functionality, the class loader beneath ApplicationClassLoader or WebappClassLoader is replaced. When an EJB-JAR is reloaded, the following files will be loaded with the default class loader configuration:
When you replace ApplicationClassLoader to reload an EJB-JAR, you must also replace the lower WebappClassLoader and JasperLoader. Therefore, when the EJB-JARs, library JARs, and reference libraries are reloaded, the reloading includes the WARs.