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: Chuck Hill <email@hidden>
- Date: Tue, 15 Jul 2008 17:24:33 -0700
On Jul 15, 2008, at 5:15 PM, Andrew Lindesay wrote:
Now, in WO 5.4 this is no longer true. When the formatter fails
to parse a string it still gets pushed into the target object. As
this is documented is must somehow be considered "expected"
behavior. Unfortunately this breaks all our apps, as no class
handles those invalid strings.
Whoa! Where is this documented? I also depend on this.
I don't see this mentioned in the 5.4.2 release notes. Is there a
bug report already? How is this meant to work now?
Also... what does "it" mean as in "...a string it still..." when the
parse-result should be a timestamp?
When it fails to parse, it tries to set the original String as the
date. Which may cause one to say, "WTF?!!?".
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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