.-Inform. Thomas CorteFon: +49-231-9703-0
[EMAIL PROTECTED] Fax: +49-231-9703-200
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
a way to
*prevent* files in the web app folder from being deleted :-)
Since I don't like multi-context solutions, I'll probably have to go for
my initial idea of backup on undeploy and restore on deploy.
--
Thomas Corte
[EMAIL PROTECTED
extension-to-mimetype mechanisms and
other stuff, something that I'd like to circumvent. But maybe I'll go
for such as servlet.
Regards,
--
Thomas Corte
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
by an
Application Listener prior the the undeployment and to restore them upon
re-deploy.
Any thoughts?
--
Thomas Corte
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
implemented in webapp X.
However, if the content is served by another webapp Y, this would
prove difficult since there is no session sharing across webapps, is
there?
--
Thomas Corte
[EMAIL PROTECTED]
-
To unsubscribe, e-mail
a minimal ROOT.war that
simply forwards to another context, since this will also cause an
unnecessary /foo prefix in every subsequent request URL.
--
Thomas Corte
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED
at what the war is about if someone just looks at the webapps drawer)
If the above is true, I wonder why the path attribute of the context
defined in META-INF/context.xml isn't simply considered in *any* case?
Shouldn't this be considered a tomcat bug?
--
Thomas Corte
[EMAIL PROTECTED
Hello,
I understand that it is possible to (re-)deploy new contexts/web
applications in Tomcat 5.5.9 without a complete server restart.
I wonder whether the same might be possible for new virtual hosts, i.e.
adding new virtual hosts/IP addresses to a running Tomcat server.
From the
