> The Java2 class loading model is for a loader to "delegate first" to it's
> parent loader. Only if the parent loader (that also delegates first to it's
> parent) can't find the class will the original loader try to load it.
>
The code in the main branch is doing exactly that - the class loader
for "core" and the class loader for "webapps" are siblings, with the
embeding application class loader as parent ( and of course, we delegate
to parent first ).
( For "trusted" applications the webapp loader is a child of the core,
that's a special exception. )
The code is not 'enabled' - it requires switching from Tomcat.java to
Main.java to start tomcat ( the LoaderInterceptor has all the code in it,
but Nacho mentioned few fixes that are also needed ).
It'll happen, but right now sorting the bugs and fixing few urgent ones (
like self-test and watchdog failures in sandboxed mode ) is more
important.
The fact that we don't have regression tests for most bugs that are
reported and fixed is really bad, and it's important to fix this in the
first place - the nightly run of watchdog and sanity and passing all tests
in all supported modes is the most important thing for me.
I'll repeat that a lot in the next weeks: if you have a bug and want to
have it fixed fast - write and send a regression test for that ( a
serlvet/jsp/whatever and a <gtest> fragment ), we'll include it in the
sanity and it'll have a fix ( that will hold and be tested nightly ).
--
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
