Doh, right, forgot about that :) How about both -
WEB-INF/chain-config.xml first, then /chain-config.xml for easier
embedding in the jar?
Don
Craig McClanahan wrote:
On Tue, 23 Nov 2004 09:58:11 -0800, Don Brown <[EMAIL PROTECTED]> wrote:
Sounds good. I would take it a step further, and, if no init parameter,
look for the chain config as "/chain-config.xml", making it possible to
provide an intelligent default. We could then, take your idea in #3,
and bundle our own "/chain-config.xml" inside Struts. Since it would be
on the classpath, it could still be easily overridden by creating a
chain-config.xml in the servlet context w/o adding any configuration to
web.xml.
Maybe default to "/WEB-INF/chain-config.xml" instead? That way the
developer can easily provide overrides by dropping a chain-config.xml
file into /WEB-INF, without making the chain configuration a publicly
available static file that can be retrieved by a browser (which would
be the case if it was in the top-level directory of the WAR).
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
