Re: [Springframework-developer] Re: ParameterNameMethodNameResolver

[Erwin V. <erw...@er...>]

First try "method", and if that's not found try "action" to deal with 
backwards compatibility?

Erwin Vervaet
erw...@er...
----- Original Message ----- 
From: "Colin Sampaleanu" <col...@ex...>
To: <spr...@li...>
Sent: Thursday, March 10, 2005 11:18 PM
Subject: Re: [Springframework-developer] Re: ParameterNameMethodNameResolver


> Matt Raible wrote:
>
>>
>> On Mar 10, 2005, at 3:04 PM, kat...@ho... wrote:
>>
>>> While on the topic, we should look at renaming the default parameter to 
>>> something other than 'action'. This clashes with the form's 'action' in 
>>> Javascript, and so is maybe not a good default. This would probably be 
>>> OK as part of a 1.2 release.
>>
>>
>> +1, I'd recommend "method" or something.  I've seen the same issue re: 
>> JavaScript, forms and button names.
>
> Hmm,
>
> I kind of like the idea, but this would probably break exsiting apps that 
> relied on the "action" default. They would not require a recompile, a 
> config change to set the property back to "action" would do, but I'm a bit 
> loath to break backwards compatibility in a .X release for something 
> that's not a true bug. Even now people can alway rename the param name.
>
> Anybody else have an opinion on this?
>
> Colin
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>