On 4/5/07, Dave Newton <[EMAIL PROTECTED]> wrote:
Having the validation files key off of method names would be pretty handy (and avoid some extra action defs).
I poked around, and it seems the design justification is to allow the methods to be validated differently in different "contexts". I do see the use case for having different validation for different methods, but I don't see a case for a context beyond the method. I would think that the method is the context. If a method needs to be validated, then it needs to be validated. I'm thinking that since annotations will focus on the method name (since they do not know the action name), then we should look at supporting configuration by method name too, so that there is at least one consistent path. :) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
