elp.
Kind regards
Tom
From: "tom ot" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List"
To: users@tomcat.apache.org
Subject: RE: what happens with the content.xml file
Date: Fri, 30 Jun 2006 09:26:24 +0200
Hi,
I simply try to match two threads...please help to discus
Hi,
there was a quiet good article in the german javamagazin.de (6.2006, page
73, title: Aktiv sondieren) hope you can get it (it is written in german).
My conclusion of this article was that there is no software jet, but there
are some very good appendages, shown by the links of Gurumoorthy.
velopers on the behavior of the
deploy path. I will say you could put version info into a
element of the WEB-INF/web.xml file if that's you're goal and it'll show up
in the manager webapp without butchering your url.
--David
tom ot wrote:
Hi Pid,
thanks again for your answer. I&
renamed the .war, you've renamed the deployed path.
It'd be easier to leave it as 'probe.war'.
You could try symlinks/url mapping to get /probe/ to map to
/probe_ver_num/.
The context path attribute behaves in a pretty restrictive way. I'm not
sure what the thinking behind it
Hi pid,
thanks for your answer. I have another question in the link you posted some
lines above there is written:
See Automatic Application Deployment for more information. This method
allows dynamic reconfiguration of the web application, since the main
conf/server.xml file cannot be reloade
