Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: ActionBean Dispatching
-
Labels:None
-
Environment:Stripes 1.4.3
Description
I am having a problem related to the execution order of two methods where each one has the @After(LifecycleStage.BindingAndValidation) annotation.
Consider method A and B.
Method A is defined at the abstract class DefaultActionBean, and method B is defined at the concrete class DefaultModuleActionBean. What i want is that method A is executed before B. The problem is that the execution order is being defined purely by the way that the reflection API returns the methods (i think). My sugestion is that these annotations can be configurable with a priority attribute just like a validation method.
I know that i could solve my case by manually invoking the superclass method, but i want that the execution of method A to be completely transparent for subclasses.