> From: Ognjen Blagojevic [mailto:ogn...@etf.bg.ac.rs]
> Subject: Re: autodeploying/unpacking ROOT.war
>
> > > debug="0" privileged="true" allowLinking="true">
> >
>
> This might be the problem. Try to remove the docBase a
Christoph Kukulies wrote:
Nothing got unpacked. I was used that whenever I put a fresh ROOT.war
(which hen contained something different than the tomcat ROOT app) it
got unpacked into a ROOT directory in webapps.
(I helped myself now in unzipping the war file).
This is typical behavior when t
Ognjen Blagojevic schrieb:
Christoph Kukulies wrote:
What again are the bits to auto-unpack/deploy a file in the webapps
directory, e.g. ROOT.war?
I looked into server.xml and there is
unpackWars="true" and autoDeploy="true" and still a ROOT.war file I
put into /usr/share/tomcat5.5/webapps rem
Christoph Kukulies wrote:
What again are the bits to auto-unpack/deploy a file in the webapps
directory, e.g. ROOT.war?
I looked into server.xml and there is
unpackWars="true" and autoDeploy="true" and still a ROOT.war file I put
into /usr/share/tomcat5.5/webapps remains untouched when I start
What again are the bits to auto-unpack/deploy a file in the webapps
directory, e.g. ROOT.war?
I looked into server.xml and there is
unpackWars="true" and autoDeploy="true" and still a ROOT.war file I put
into /usr/share/tomcat5.5/webapps remains untouched when I start
tomcat5.5 again. (It's Deb
