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=25008>. 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=25008 Enable symbolic links: Release notes not clear about "allowLinking" flag. ------- Additional Comments From [EMAIL PROTECTED] 2003-11-26 11:56 ------- For the likes of me: It is not enough to specify this just for the ROOT context, the same <Resources>... stuff needs to be present in *every* context for which you'd like symbolic links to work. As far as I know, you need to mention those <Context>s for which you want symbolic links in your server.xml, one at a time. E.g.: <Context path="/tomcat-docs" docBase="tomcat-docs" debug="1"> <Resources className="org.apache.naming.resources.FileDirContext" allowLinking="true" /> </Context> <Context path="/jsp-examples" docBase="jsp-examples" debug="1"> <Resources className="org.apache.naming.resources.FileDirContext" allowLinking="true" /> </Context> In other words, appearently you cannot automatically deploy anything that needs symbolic links by just placing it in webapps/ . Related bugs: Bug 25010, symbolic links should be supported through <DefaultContext>, which would give us symbolic links _and_ autodeployment. Bug 25011, this flag should be documented for <Resources>. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
