Hmmm...
I did some reviews of CVS for the code which sets the context dir
FilePermission. I had made a cut n paste mistake when changing code related
to this which would have prevented the context dir FilePermission
from being created. This bug only existed for 6 hours in CVS before
I fixed it.
On Thu, 24 Oct 2002 22:59:59 -0500, Glenn Nielsen [EMAIL PROTECTED] said:
Gettting the latest version from CVS won't fix your problem. I still
think the problem is somewhere in your configuration.
I've installed the 4.1.12 tarball from the website and am running it
without modification other
The ProtectionDomain shows that Jasper2 is creating a read FilePermission for the scratch
(work) dir. But you are correct, there is no read FilePermission listed for the context
directory.
The same block of code in org.apache.jasper.compiler.JspRuntimeContext which creates the
scratch (work)
Aditya wrote:
Glenn,
On Thu, Oct 24, 2002 at 10:03:47AM -, [EMAIL PROTECTED] wrote:
This must be a problem in your local system configuration.
Check the unix file ownerhsip and permissions for test2.new.
I've done that and the fact is that it works fine without the security
Aditya wrote:
Glenn,
On Thu, Oct 24, 2002 at 10:03:47AM -, [EMAIL PROTECTED] wrote:
This must be a problem in your local system configuration.
Check the unix file ownerhsip and permissions for test2.new.
I've done that and the fact is that it works fine without the security manager
so
