A Web application’s custom class list must include any classes that must be reloaded when the Web application is refreshed. For example, servlet implementation classes, utility classes called by servlets and JSPs, and stub classes for component invocations should be in the custom class list.
If you deploy classes and JAR files that the standard Web application deployment locations, you do not need to explicitly list them in the custom class list. The standard Web application deployment locations are under your Web application’s context root, the EAServer subdirectory:
Repository/WebApplication/WebApp
Where WebApp is the Web application name. Deploy classes and JAR files to these subdirectories of the context root:
WEB-INF/classes for class files.
WEB-INF/lib for JAR files that contain archived class files.
EAServer automatically adds classes and JAR files that are deployed in the standard locations to the custom class list. Use these locations to deploy classes and JAR files that are specific to your Web application. These directories are equivalent to the like-named directories in a J2EE WAR file.
For classes that are also used in EJB or Java components or other Web applications, you can deploy classes or JAR files in one of the locations below. For example, if your servlet calls an EJB component, you may want the servlet and component to use the same copies of the component stub classes. You must explicitly list these classes or JAR files in your Web application’s custom class list:
The EAServer java/classes or html/classes directory, for class files that are also used by components.
The EAServer java/classes or java/lib directory, for JAR files that are also used by components.
The EAServer extensions subdirectory for JAR files used by multiple Web applications, as described in “Using Java extensions”. These JAR files can be used by any Web application that lists the JAR file name in the custom class list.
Though a component and Web application may custom load the same classes, to enable sharing of one copy of each class, you must configure the same custom class list entries in parent entities up to a common ancestor entity, as described in “Custom class lists for packages, applications, or servers”.
