Thanks for your reply Tim.
Tim Penhey wrote:
Andrew Watters wrote:
In this case the webapps directory is entirely empty, I delete the
ROOT folder as part of the publish procedure and there are no other
apps configured except for the manager and admin ones.
What about the XML configuration file i
Andrew Watters wrote:
In this case the webapps directory is entirely empty, I delete the
ROOT folder as part of the publish procedure and there are no other
apps configured except for the manager and admin ones.
What about the XML configuration file in
$TOMCAT_HOME/conf/Catalina/localhost
Does i
Thanks. Sorry that's just my poor typing. It actually is ROOT.war. If I
name it back again it unpacks fine! Aaagh, my head hurts now.
Ben Souther wrote:
try ROOT.war
On Mon, 2004-11-08 at 10:27, Andrew Watters wrote:
Apologies, I replied before but it never appeared, trying again...
I renamed
I renamed it to ROOT.WAR. The webapp used to be named like this and
previously worked fine. It's now called ROOT-1.0.WAR. The new name is a
result of moving to maven and it appending the version number.
Ben Souther wrote:
What did you rename it to?
On Mon, 2004-11-08 at 09:46, Andrew Watters wr
try ROOT.war
On Mon, 2004-11-08 at 10:27, Andrew Watters wrote:
> Apologies, I replied before but it never appeared, trying again...
>
> I renamed it to ROOT.WAR. The webapp used to be named like this and
> previously worked fine. It's now called ROOT-1.0.WAR. The new name is a
> result of mov
Apologies, I replied before but it never appeared, trying again...
I renamed it to ROOT.WAR. The webapp used to be named like this and
previously worked fine. It's now called ROOT-1.0.WAR. The new name is a
result of moving to maven and it appending the version number.
Ben Souther wrote:
What di
In this case the webapps directory is entirely empty, I delete the ROOT
folder as part of the publish procedure and there are no other apps
configured except for the manager and admin ones.
Shapira, Yoav wrote:
Hi,
Well, that explains something :) So what is tomcat seeing in the WAR
that it r
Hi,
>Well, that explains something :) So what is tomcat seeing in the WAR
>that it refuses to unpack it after renaming?
A directory with that name already existing. Tomcat won't overwrite
such a directory if it exists.
If your app is Spec-compliant, considering setting unpackWARs="false"
for y
Well, that explains something :) So what is tomcat seeing in the WAR
that it refuses to unpack it after renaming?
Shapira, Yoav wrote:
Hi,
I have a WAR which tomcat recognises and unpacks correctly. When I
rename the WAR tomcat no longer unpacks it. Is this expected behaviour?
I've had a look
Hi,
>I have a WAR which tomcat recognises and unpacks correctly. When I
>rename the WAR tomcat no longer unpacks it. Is this expected behaviour?
>I've had a look in the 2.4 servlet spec and haven't been able to find
>anything on this topic. Is there a work around that will allow me to do
>this?
What did you rename it to?
On Mon, 2004-11-08 at 09:46, Andrew Watters wrote:
> I have a WAR which tomcat recognises and unpacks correctly. When I
> rename the WAR tomcat no longer unpacks it. Is this expected behaviour?
> I've had a look in the 2.4 servlet spec and haven't been able to find
I have a WAR which tomcat recognises and unpacks correctly. When I
rename the WAR tomcat no longer unpacks it. Is this expected behaviour?
I've had a look in the 2.4 servlet spec and haven't been able to find
anything on this topic. Is there a work around that will allow me to do
this?
Thank y
12 matches
Mail list logo
