[cosmo-dev] cosmo webapp packaging

[Brian Moseley]

On Nov 16, 2007 10:54 AM, Benoit Mercier <Benoit.Mercier at usherbrooke.ca> wrote:
> Thank you for your quick reaction.  I completly agree with your comments
> concerning log4j and cosmo.properties.
> If you can manage to do the move, it would be a nice improvement of the
> cosmo deployment in existing tomcat environments.

i put some effort into context.xml configuration this morning and ran
into a roadblock concerning development configuration. basically, I
can't think of a good way to manage context.xml in svn and in our
source code filesystem layout so that Cosmo developers can have a
custom configuration for dev (say, pointing at local mysql) versus the
release one (embedded Derby).

what could work is to not put context.xml into
src/main/webapp/META-INF but rather copy it into place when the war is
being built. developers could hand-create their own
$CATALINA_HOME/conf/Catalina/localhost/chandler.xml, but the released
war would have a META-INF/context.xml in it. snarf's server.xml would
not have any <Context> or <GlobalNamingResources>, though it would
still have a commented-out secure connector and an access log Valve.

this would also let devs put their cosmo.properties wherever they
want, like say ~/.chandler/cosmo.properties, since this would be
configured in a dev-specific chandler.xml. the only customizations of
the snarf build would be making a symlink in $CATALINA_HOME/webapps to
the exploded webapp and dropping in the custom chandler.xml (or
symlinking it).

what do y'all think? bear, is it doable to make the cosmo packaging
step copy a non-filtered context.xml into place when the war is being
created?