Jim Goodspeed wrote:
Are there any pros and cons running unpackWARs one way or another? It
seems
like keeping unpackWARs="false" might be a little cleaner (not having to
remove expanded directories when deploying a new war file), but I wasn't
sure if there were any performance hits associated with running this set to
false.
I've been running with packed WARs for a while, and just ran into an
issue with Spring's log4jContextListener. It demands that the war be
unpacked so it can reference the application root as an absolute
pathname. Tsk!
I agree that leaving them packed is neater, and I like not having to
worry about stale files in an exploded app directory, but I'm careful to
delete the exploded directory most of the time anyway.
Having them unpacked should have a slight performance advantage because
the files don't have to be searched and unpacked from the WAR when
they're referenced.
Best regards,
Mojo
--
Morris Jones
Monrovia, CA
http://www.whiteoaks.com
Old Town Astronomers: http://www.otastro.org
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
