I haven't actually look at the code yet, but as I understand it, wildcards are not even considered unless no other match is found. In which case you would be getting an error page anyway.
So I don't think there's any performance impact... unless you're in a hurry to see that error page :-) Steve > -----Original Message----- > From: Robert Leland [mailto:[EMAIL PROTECTED] > Sent: August 11, 2003 7:41 PM > To: Struts Developers List > Subject: Re: Wildcard-matched actions (again) > > > Don Brown wrote: > > >Heh, thankfully no. :) In fact, that's one of the reasons I'd like to > >incorporate this into Struts itself to remove that alternate processor > >requirement. > > > >The patch adds a couple of lines to RequestProcessor.processMapping() to, > >in the case of no direct mapping found, try to match any wildcards. All > >of the logic of wildcard mapping is stored in a helper class to keep > >RequestProcessor as clean as possible. > > > >Don > > > How about an option to turn it off ? Having something infinitely > configurable is good right ;-) ! > But seriously, if there will be noticeable overhead the ability should > be able to be turned off. > In fact once struts configuration is frozen then it should be able to > detect whether it needs > to search for wild card matches or not. > > -Rob > > -- > Robert Leland [EMAIL PROTECTED] > ------------------------------------------ > Java, J2EE, Struts, Web Application Development > > 804 N. Kenmore Street +01-703-525-3580 > Arlington VA 22201 > > > > --------------------------------------------------------------------- > 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]
