Friday, August 30, 2002 07:27 AM
The classloader hierarchy is pretty much appserver-specific.
Usually, I guess, the appserver creates one classloader for each application (.ear) and one child-classloader for each web-app (.war) within the application. The application classloaders are children of the system classloader.
When a classloader tries to load a class, it doesn't ask from its children, only from its parent classloader, so keep this in mind if/when you run into problems.
There are a couple of articles around the web about the J2EE classloader hierarchies of some appservers.