Remy Maucherat wrote:
Remy,
What I am trying to do is start a discussion of _what_ the behaviour
should be,
so it can be fixed. I already consider the current behaviour to be broken.
I'm mixed on the subject. Craig implemented it that way, so I want to hear
his opinion on the
On Fri, 2 Mar 2001, Craig R. McClanahan wrote:
Yes sure. I think the best would be not to unpack the WARs (it's a lot
cleaner).
+1, as long as we can keep performance reasonable.
Well, memory's cheap. You can always just read the whole WAR in.
Then you'll get great performance.
On Fri, 2 Mar 2001, Craig R. McClanahan wrote:
Yes sure. I think the best would be not to unpack the WARs (it's a lot
cleaner).
+1, as long as we can keep performance reasonable.
Well, memory's cheap. You can always just read the whole WAR in.
Performance should be good with WARs
What is the expected behaviour of Tomcat 4 when starting/stopping
in regards to unpacking war files.
I noticed what to me seems like strange behaviour.
The Host is configured in server.xml with unpackWARs="true".
ls of webapps before starting tomcat, notice that some of the war
files are
I consider this a bug. Tomcat should not be removing contexts that have
been expanded out into a directory in webapps.
If unpackWARs="false", then nothing is expanded out into webapss, the war
file is expanded out as needed into the work dir, correct?
The JARs are indeed expanded as a
If unpackWARs="false", then nothing is expanded out into webapss, the war
file is expanded out as needed into the work dir, correct?
The JARs are indeed expanded as a temporary fix for Jasper. There is hope
that we can perhaps use a tweaked version of javac which would load classes
from a
Remy,
What I am trying to do is start a discussion of _what_ the behaviour should be,
so it can be fixed. I already consider the current behaviour to be broken.
For example deploying a war on starutp, then undeploying it on shutdown
adds unnecessary overhead to the tomcat start/stop processing.
If unpackWARs="false", then nothing is expanded out into webapss, the
war
file is expanded out as needed into the work dir, correct?
The JARs are indeed expanded as a temporary fix for Jasper. There is hope
that we can perhaps use a tweaked version of javac which would load
classes
from
