> From: "Jeff" <[EMAIL PROTECTED]> > Sent: Thursday, January 30, 2003 3:00 PM > Subject: force automatic physical unpacking of warfiles amidst existing context definition?
> Is there any way to force Tomcat 4.1.18 to physically unpack .war files it finds in /webapps > amidst the presence of *ANY* kind of durable server-specific configuration for that warfile's > context? So, let me get this straight and clear. You have a webapp in a .war file. You have parameters specific to the context that you wish to not change constantly, so you want these configured outside of the war file. You want to have Tomcat unpack the war file, and in a particular place (/webapp). Have I got it right? All of this raises, to me, the red flag of why you a) want the webapp exploded and b) you seem to care WHERE it gets exploded. Ideally, neither of these should matter because according to the spec you don't have any real control over where or when it happens, so you shouldn't make any assumptions about the process. But, anyway, why not simply unpack it yourself as part of your deployment? Then you have full control over the situation. I found that if you create a context for a war file, that Tomcat explodes parts of it into its Work directory, as it frankly has no place else it's allowed to go, and then it doesn't seem to extract anything save the WEB-INF directory. Also, you need to restart Tomcat for it to see a change in a webapp war anyway, correct? It's not like detecting a changed class or JSP file. Webapps tend to be a bit more complicated (or at least have the potential of being more complicated). Regards, Will Hartung ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
