Stuart Roebuck wrote:
> Craig,
>
> Here's one step towards what you were asking for. It's a standalone test case of
>the problem. I've written this because, judging from some of the issues that were
>occuring with Cocoon, I have a feeling that this problem is System/Java version
>dependent. The problem has been seen on Solaris, MacOS X and Windows with versions
>1.2.2 and 1.3, but it may be only in certain combinations.
>
Thanks for the test case. I've got equivalent behavior to yours (classloader 1 fails,
classloader2 succeeds) on:
* Linux, Sun JDK 1.2.2 and Sun JDK 1.3.0
* Win98, Sun JDK 1.2.2 and Sun JDK 1.3.0
> If this test case reproduces the problem on your system, then were going in the
>right direction. If not, then we'll never produce a test case for you to be able to
>test.
>
Yesterday, I committed the Tomcat 4.0 changes to use getCanonicalPath() instead of
getAbsolutePath() in all the relevant cases. Looking at what we're seeing, I would
bet you were certain to have problems (on the affected platforms) before if your
CATALINA_HOME had "../" elements, or if the document root of a particular web app had
them.
Have you had a chance to try the updated code yet? The nightly build from last night
is probably the easiest way.
Craig
