And as usual, you have the solution :-) Ok, so now I'm checking if the errors
array is empty before calling saveChanges, and everything is beautiful in
Wonderland.
> I hope I am understanding you correctly Pascal, so……..
>
> Form values are pushed in takeValueFromRequest using the
> validateTa
I hope I am understanding you correctly Pascal, so……..
Form values are pushed in takeValueFromRequest using the
validateTakeValueForKey( … ) …… only then will your WOComponent
validationFailedWithException be called.
So BEFORE you call ec.saveChanges, you need to check if you have validation
And you are overriding Application.handleException to return a different
component based on the number of items in your session.errors()? I'd suspect
that the order of things might be wrong here...
On 04.10.2011, at 14:42, Pascal Robert wrote:
>
> Le 2011-10-04 à 08:30, Marius Soutier a écrit
Le 2011-10-04 à 08:30, Marius Soutier a écrit :
> Stab in the dark - the call to super?
Tried that too, didn't change anything. super will call
session.validationFailedWithException, which will call
application.validationFailedWithException
I'm doing something similar to the SecretPal example
Stab in the dark - the call to super?
On 04.10.2011, at 14:23, Pascal Robert wrote:
> I guess working with REST and calendars made my brain to forget how to do
> things with stateful components... I need to trap validation exceptions when
> required attributes are missing and ec.saveChanges() i
I guess working with REST and calendars made my brain to forget how to do
things with stateful components... I need to trap validation exceptions when
required attributes are missing and ec.saveChanges() is called, so in my
superclass for my components, I did:
public void validationFailedWith
