>>> [EMAIL PROTECTED] 10/19/04 1:19 PM >>> >You can, and Tomcat does this, for the relevant >parts of the WAR. But a WAR can contain an >unlimited amount of resources, including for >example 2 GB of static .html files ;)
Heheh, yeah, and i *could* write my entire web application using inner classes (and doing so would be tremendously retarded), but does that mean we should not allow any inner classes? Trying to run a 2GB war file w/o unpacking it would be equally retarded. :-) I admit, that is not the greatest analogy, but it makes the point. Common sense should dictate how you deploy your application, not worst case scenarios. Preventing people from doing bad things is a good thing as long as they can still do the good stuff. ;-) >The WAR file does not *have* to be unpacked. >In fact, the Servlet Spec requires its Containers >to support running a packed WAR, and not vice >versa. Whether to unpack a WAR partially, fully, >transparently, or optionally are all Servlet >Container implementation choices. Umm, huh? So why does it always unpack it? I am sorry if I sound like an ungrateful pig. Don't get me wrong, I love tomcat, and it does 99% of what I want. I am just an ungrateful pig who wants 100%. ;-) Larry --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
