> I have another question, which has been nagging me for
> a while: Why does the class loader for a web-app "see"
> the classes in the lib folder of the servlet engine
> (or the classpath of the java engine).
The problem will be resolved in the main tree ( most of the
code is there, I think Nacho was going to do it, or I ).
We use URLClassLoader - with no "trick".
The problem is that all files in lib/ are included in
CLASSPATH by the starter.
The solution is to use a different startup script,
and construct a different class loader hierarchy -
i.e. the webapplications will still have a parent loader
including the files in CLASSPATH / embeding application, but the
core/modules will be in a separate ( paralel ) loader.
The change is not difficult, but requires changing the
startup scripts and tomcat.startup.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
