Peter Bliznak wrote:
It is across entire app (there are many dozen of actions) - every
single action has to have same behavior - 3 crosses go and try again.
It's app for changing personal info on government issued documents -
sorta wizard like thing. I can see how I can do it by keeping eye of
parameters - but I am looking for cleanest possible implementation.
But if I decide to modify default stack I am not certain what might
be consequences for the rest of app.
None, if you do it right.
Since it's across the entire app I'd go the interceptor route--but
you're still going to have to either use a hidden parameter, keep
something in session, or whatever. Both have their advantages and
disadvantages, but are basically the same complexity.
I'd probably consider modifying the <s:form> template to insert a hidden
parameter, but that leaves it vulnerable to someone spoofing the
validation count--if that's an issue. Otherwise you'd have to track a
session variable, re-initialize it when a form is displayed for the
first time, and so on.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
