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=4829>. 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=4829 Automatic deployment of war files does not work properly [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2001-11-15 13:34 ------- We had already tried your proposal, but it does not work. We have not changed the parameter unpackWARs (which -I think- is responsible for the unpacking), but Tomcat does not unpack the webapp: <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true"> Is there any other way to let Tomcat extract the WAR file? We _must_ define a context for lexis, to do the folowing: 1) avoid the sessions to be persisted and reloaded (saveOnRestart="false") when Tomcat is shut down and restarted (Just because we do not only use struts: we also use log4j, which is not Serializable, and at higher levels the PersistentManager declarations seem not to work) 2) to log4j the lexis application to a specific file/directory 3) to use application parameters ((Without defining a context for the webapp lexis Tomcat DOES extract the WAR file. Only when I __define__ a context it DOES NOT!!)) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
