SERVER
All modules on the server have visibility of all other modules on the server.
APPLICATION
All modules are visible to all other modules within the same enterprise application.
Modules that are part of a different enterprise application are not visible.
APPLICATION--J2EE
To enable Application--J2EE visbility mode define Java system property
com.ibm.ws.classloader.J2EEApplicationMode with a value of true
on the JVM Settings
tab of the application server.
EJB modules are visible to all other modules within the same enterprise application. EJB modules that are part of a different enterprise application are not visible. Web modules are not visible to other Web modules or to EJB modules. Dependencies (locations specified in module classpaths) are visible to all modules in the application.
MODULE
Module visibility has been deprecated. Application servers using module
visibility should switch to Application--J2EE visibility.
Modules are not visible to each other. Visibility to other modules in the application is only achieved when MANIFEST Class-Path entries are added to a module. This is done by setting the Classpath property on the EJB module or WAR module in the Application Assembly Tool (AAT).
COMPATIBILITY
This value provides compatibility for applications ported from WebSphere
Application Server Version 3.5 and 3.0.2. In this mode, all EJB modules have
visibility of all other EJB modules, even across different
applications, and all Web Application modules have visibility of all EJB modules.
Dependencies (locations specified in
module classpaths) are visible to all modules in the server.
Portable J2EE applications should be written visibility. The other modes are provided to accomodate applications that have different visibility requirements that cannot be modified. See Guidelines for packaging classes for more information on how to package J2EE applications.
The default module visibility for WebSphere Application Server Version 4.0 Advanced Edition is MODULE.