Hi, When you deploy an application as a WAR, you have no control over how the server will explode it, if at all. You may not even have read permission to the files in it. You definitely should not have control over the internal mechanisms used by the servlet container to deploy your WAR file.
As an alternative, consider creating a directory with these script files. Pass this directory as an init-param to one of your servlets. That should address the permissions problem and will be container-independent. However, you lose having just one WAR file contain your whole application. ;( As an aside, it may be a serious security hole to have your web application run any sort of OS scripts. You should be sure to minimize the use of such scripts and carefully scrutinize them for bugs, buffer overruns vulnerabilities, etc... Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: javadev82 [mailto:[EMAIL PROTECTED]] >Sent: Sunday, July 21, 2002 6:51 AM >To: tomcat- user >Subject: WAR > >Hello, I have a application which I deploy as a WAR file. >The application includes some executable script files. When Tomcat >expands the WAR file the permissions on the script files are changed >so they are no longer executable. Is there a way to prevent this from >happening? > >Thanks, >Bill > > >-- >To unsubscribe, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
