On 7/25/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
@Action to mark it as an Action method?
On 7/25/06, Bob Lee <[EMAIL PROTECTED]> wrote:
+1 for @Action
Action is already so overloaded, it's painful to see us trying to reuse it again in another context. Sure, we have an Action interface, but we also have action elements, and here what we are really marking is the "method" property of the action element. If we wanted to use Struts 2/Webwork 2 terminology, a likely term might be @method. But, marking a method method seems redundant :) If it's acceptable to use periods in annotations, the next most likely suspect might be @action.method, to corresponds with the Struts configuration. Though, I would strongly suggest that we try to follow the Stripes annotations wherever possible. And if there's a hard reason why we want to use a different term, we should work with Tim on an alternative. There's really no reason to have two annotation APIs that are trying to do essentially the same thing. * http://stripes.mc4j.org/confluence/display/stripes/Annotation+Reference -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
