|
Problem |
Setting the "Module visibility" value to "Server" for an
Application Server does not ensure that all of the Java(TM) archive (JAR)
files that are contained within the server will be loaded. |
|
Solution |
Problem:
The JavaServer Pages (JSP) files cannot access the required classes
because server module visibility accesses only one class loader. If no
application loads a class, the JSP file will not be accessible to any
running class.
Scenario:
- EAR1 contains JAR files a.jar, b.jar and c.jar.
- EAR2 needs all of these JAR files to function.
- Because EAR1 is provided by a third party (for example),
it does not necessarily use the JAR files within its modules. Therefore,
it is not included in any CLASSPATH for the modules within EAR1.
- The module visibility for EAR files installed on this
server is Server.
- Finally, a JSP file within EAR2 cannot access the JAR
files.
Solution:
Add the JAR files a.jar, b.jar and c.jar to the CLASSPATH in one of the
Web module manifest files in EAR1. Even if this module does not reference
a class in the JAR file, it will support the class loader to access these
classes for all Web modules in the Application Server. |
|
|
|
|
|
|