Hi all.
Just noticed (after scratching my head for a couple hours) that I had
misunderstood the statement is invoked when validation fails in the
Validation Reference wiki. Can I have a wiki user to try to clarify it?
User: hlopf
Mail: hector.lo...@unileon.es
Thanks.
---
Hi Hector,
I am not a writer of this entry but I believe it means method will be
invoked when validation not passes (fails).
So, lets say you have a form that contains some validation errors,
normally,
user will be presented with your form and validation errors.
However, if you implement Vali
Thanks for the reply.
My error was to believe that handleValidationErrors was called when
validation fails, when, in fact, the method is called whenever there are
ValidationErrors in the actionbeancontext (as clearly stated in the
javadoc, btw). This can seem the same at first sight, but th
shot in the dark(haven's used this before):
could it be because validation errors are still present..?
what happens when you try:
*
public* Resolution handleValidationErrors(ValidationErrors errors)
*throws* Exception {
String event = getContext().getEventName(); // First
validat
Fortunately, they are :), let me try to show the big picture:
I was using the same action to paint the edit screen and to persist edited
data (different events). The jsp accesses user collections and I need to
pass through an action before painting the screen. I needed the errors for
reporting
Thanks muchly Freddy :)
By using the autocomplete="off" and the dynattr tld, I have solved
this problem (at least until the browsers change the way they treat
this non-standard parameter).
Chris
On Fri, Dec 19, 2008 at 4:08 PM, Freddy Daoud wrote:
>> On
>> a stripes note, I tried using the non-
