We are at the point where in many cases we will want an action to 
1. implement Action (for configuration by convention purposes) and also 
2. use the @Action annotation 
So we are faced with either using fully qualified names for one of the 
'Action's or taking the route of extending ActionSupport and losing the chance 
to extend anything else. Perhaps in later versions we could have fewer things 
called Action?
Chris M


Reply via email to