2013/10/3 Steven Benitez :
> Why not just have an @ActionMethod annotation? If its on the action method,
> you can invoke it, if not, you can't. The global config option for allowed
> methods sounds reasonable (e.g., execute, input, etc.)
Nice idea and quite simple :-) What about "allowedActions"
I like that WAY better. Instead of using opaque strings in @Action, use
@ActionMethod on the destination methods. +1
On Fri, Oct 4, 2013 at 4:31 AM, Lukasz Lenart wrote:
> 2013/10/3 Steven Benitez :
> > Why not just have an @ActionMethod annotation? If its on the action
> method,
> > you can inv
I suggested this because I wrote an interceptor to require the
@ActionMethod annotation years ago to lock down DMI. The upside to a
separate annotation was that it was completely compatible with XML
configuration (which I use). It also had a nice benefit of being
documentation, as well. No ambiguit
