DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13907>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13907 security manager does not give read permission on a context by default ------- Additional Comments From [EMAIL PROTECTED] 2002-10-23 21:43 ------- You are correct. The behavior should be for the container to programmatically grant a file read permission for a context's codebase in the context's docBase directory (and all subdirectories). You do not need to explicitly grant the each app a file read permission explicitly, unless you need to read outside of the docBase directory. I can confirm that Tomcat 4.0.2b1 - 4.0.5 behaves this way, and I believe 4.1.x is supposed to. If not, it's a bug. -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
