I found the solution, though not a completely satisfying explanation. Thought I'd post what I found in case anyone else ever encounters something similar.
By changing the "unpackWARs" attribute of the Host element in my server.xml to "false", I got back the behavior I had seen in earlier releases (my war file is no longer unpacked under the /webapps folder).
Going back through old versions of my server.xml (kept in CVS), I find that the unpackWARs attribute had always been present, and had always been set to "true". So I still don't know what changed with 4.1.24 to change the behavior, but I found a way to get back my old behavior. In fact, it seems that the unpackWARs behavior was not behaving properly in the old release, since the deployed war was *not* unpacked.
What still seems odd, though, is that the out-of-the-box installation of 4.1.24-LE seemed to install with unpackWARs to true, which caused my war files to get unpacked. This seems inconsistent with the documentation, and with the experiences of at least one other user - where the war was not expaned. So I don't know what I did wrong, or have configured wrong.
So, I don't know what happened, but am happy that I got my old behavior back on the new release!
PC
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
