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
Just so you know, these recent changes to correct the paths has screwed up
Turbine. :-) I was depending on a path to have a ./ in it and now that is
removed and therefore, Turbine is broken because the paths don't get
generated properly.
I'm not complaining because I should probably fix it in
Jon Stevens wrote:
fyi, the difference is that I had to add a "./" to the front of a parameter
to a file that I was passing in...
init-param
param-nameproperties/param-name
!-- This is relative to the docBase --
param-value
on 12/22/2000 12:25 PM, "Craig R. McClanahan" [EMAIL PROTECTED]
wrote:
Are you accessing the properties file via ServletContext.getResource() or
ServletContext.getResourceAsStream()?
Neither actually. We are using JServ's old code for loading properties so it
is still direct file/io access.
Thanks Craig,
I'm in the middle of some tricky development with Cocoon at the moment and I don't
wont to risk breaking my environment just at this instant.
I hadn't consciously had a problem with this on Tomcat (only specifically within the
internal ClassLoaders of Cocoon). I only mentioned
Stuart Roebuck wrote:
In the course of fixing a problem I was having getting Apache Cocoon to run, I came
across a bug in Java in the File.toURL() method. This fault, combined with the use
of the URLClassLoader resulted in a classloading issue.
Stuart,
I'm trying to create a simple,
In the course of fixing a problem I was having getting Apache Cocoon to run, I came
across a bug in Java in the File.toURL() method. This fault, combined with the use of
the URLClassLoader resulted in a classloading issue.
As a result of finding this bug I thought I would check through the
