Am 19.03.2012 09:28, schrieb Maurizio Cucchiara:
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Linkedin :http://www.linkedin.com/in/mauriziocucchiara
Maurizio Cucchiara
We could implement a "most specific take a precedence along the path"
policy (though I don't know how ATM :) ), could you please file an issue on
jira [1]?
[1] https://issues.apache.org/jira/browse/WW
Definitely not the best or most elegant solution, but some sort of
@matchPriority(A)
where A is a pos. int value (or zero) and if A > B, A fires before B
could do the trick (for now)
Usage scenario:
@Action(value="some/{stuff}", results={@Result(location ="result.jsp")})
@matchPriority(0)
public String action1() {....}
@Action(value="some/useful/{stuff}", results={@Result(location
="result.jsp")})
@matchPriority(1)
public String action2() {....}
This way the second action method fires before the first one.
Mounir
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
