On Tue, 23 Mar 2004, Craig R. McClanahan wrote:

> Quoting Ted Husted <[EMAIL PROTECTED]>:
>
> > On Tue, 23 Mar 2004 11:53:55 +0100, Filippo Munafò wrote:
> > > Perfect! What you did in JSF is exatcly what we need:
> > >
> > > "the controller servlet automatically recognize 'META-INF/struts-
> > > config.xml' resources in any JAR files that were included in the
> > > application."
> > >
> > > When in struts?
> > >
> > > Can I help?
> >
> > I think we do the same sort of thing in Commons Chain, n'est pas?
> >
>
> This particular functionality was in relationship to automatically finding and
> loading struts-config.xml files (contributed by JAR files dropped in to the
> WAR) without having to explicitly note them in context init parameters.  It
> doesn't really relate to per-request processing.
>
> I can't do this today, but anyone who wants to help on this need only submit an
> enhancement request (with a patch) to ActionServlet.init() to scan the
> configuration resources in addition to what it already does.  The secret sauce
> is to use ClassLoader.findResources() to get the list of URLs to be processed.

Before anyone does dash off and write this, I'd like to have a brief
discussion about this in relation to multi-module applications, and
removing any need to modify web.xml when adding or removing modules. This
is something I did in a project about a year ago, very successfully, so I
think it's worth adding to the Struts core.

In a similar vein, I'd like to talk about separating out the config
reading somewhat, to allow for alternative mechanisms.

Unfortunately, I'm about to go off to a 4-hour meeting ;-( so I can't
expound further right now. More later...

--
Martin Cooper


>
> > -Ted.
>
> 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]

Reply via email to