Re: What is the best way to handle invalid values from a WOTextField?
Re: What is the best way to handle invalid values from a WOTextField?
- Subject: Re: What is the best way to handle invalid values from a WOTextField?
- From: Andrew Lindesay <email@hidden>
- Date: Thu, 17 Jul 2008 08:11:22 +1200
Hello Guido;
I store the bad value in "validationFailedWithException(..)" and then
when the key-path hits the component controller again during the
"appendToResponse(..)" phase, it regurgitates the bad value to the
element (WOTextField usually) rather than taking it from the EO. This
way "bad data" can make its way back onto the page without every
mucking up an EO's clean state. In the case of a formatter, if it
experiences a format exception, it seems to let the string through.
This seems to be workable for me over a wide range of situations.
cheers.
I am guessing this is an attempt to deal with the problem of the
input value getting discarded if it failed to format. It is
reasonable to want to show the invalid value to the user with a
message and allow them to edit it into the correct format. This is
just the wrong way to do that.
Hmmm, is there any other way than binding to a string variable in
the EO and if it parses set the date / number value from it and if
not throw an exception but keep it in the variable? If I attach a
formatter to a text field because I NEED to format a string into a
number or date object, it is just plain impossible to push that
value into the object (ClassCastException). So do I not understand
how that was ever intended to work or is it really just a bad idea
in the first place?
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden