Actually, the way I wrote the code, wildcards are only matched if an exact match cannot be found but before the "unknown" action mapping is executed. So, there is no performance penalty for existing applications that use specific matchings. The order:
- Try to find an action mapping that matches the path exactly - Try to find an action mapping using wildcard matching - Try to locate the mapping for "unknown" paths Don On Saturday 05 July 2003 08:31 am, Craig R. McClanahan wrote: > On Sat, 5 Jul 2003, Niall Pemberton wrote: > > Date: Sat, 5 Jul 2003 01:32:45 +0100 > > From: Niall Pemberton <[EMAIL PROTECTED]> > > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > > To: Struts Developers List <[EMAIL PROTECTED]> > > Subject: Re: [PROPOSAL] Wildcard-matched actions > > > > I like it. > > > > Perhaps you should create an enhancement request in bugzilla and attach a > > patch with your code. > > The idea makes some sense, and gets us more towards a general purpose > "site map" approach to mapping arbitrary URLs to arbitrary actions. My > one concern will be performance related, since this kind of matching will > be slower than the existing approach. This could perhaps be alleviated by > having a per-module-setting (or some smart initialization code) that only > used the wildcard matching code if the module actually has some actions > that need it, and uses the optimized version otherwise. > > > Niall > > 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]
