On Monday 02 Dec 2002 5:01 pm, Jeanfrancois Arcand wrote:
That's the proper behaviour. By default, a web application is only able
to read under the context under which it was deployed. If you want to
grant access to the /tmp !*be carefull*!, add the following in your
catalina.policy file:
Hi,
However, if no value is specified in the web.xml, then currently the
hard-coded default is /tmp; the thinking being this is it's usually a
safe
place to write stuff.
How about, if no value is specified in web.xml, use
javax.servlet.context.tempdir? That's always available as if it were
Simon Brooke wrote:
On Monday 02 Dec 2002 5:01 pm, Jeanfrancois Arcand wrote:
That's the proper behaviour. By default, a web application is only able
to read under the context under which it was deployed. If you want to
grant access to the /tmp !*be carefull*!, add the following in your
...
root cause
java.security.AccessControlException: access denied (java.io.FilePermission
/tmp read) at
java.security.AccessControlContext.checkPermission(AccessControlContext.java(
Compiled Code))
Now if I understand what's going on there, the servlet is falling over
because it can't read /tmp
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935
)
... usual stuf...
root cause
java.security.AccessControlException: access denied (java.io.FilePermission
/tmp read) at
java.security.AccessControlContext.checkPermission(AccessControlContext.java(
Compiled Code))
Now if I understand
ChemInformatics
-Original Message-
From: Simon Brooke [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 02, 2002 11:40 AM
To: 'Tomcat Users List'
Subject: Access denied... to /tmp !?
Hi
I've been running things under various versions of Tomcat for a long
time
now, but it's always been Tomcats I've
