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: Lachlan Deck <email@hidden>
- Date: Wed, 16 Jul 2008 15:10:35 +1000
On 16/07/2008, at 2:59 PM, Chuck Hill wrote:
On Jul 15, 2008, at 9:51 PM, Guido Neitzer wrote:
On 15.07.2008, at 18:36, Chuck Hill wrote:
I just tested this now and got a class cast exception in the
released version of 5.4.2 when I typed a string into a text field
with a formatter on it:
java.lang.ClassCastException: java.lang.String
[2008-7-15 17:19:11 PDT] <WorkerThread13>
java.lang.ClassCastException: java.lang.String
at
net
.foo
.core
.searchfields.DateSearchField.qualifyOnValue(DateSearchField.java:
64)
That is just an out and out bug. I don't see how it can be fixed
other than by replacing WOTextField
Reported as 6078428.
AFAIK, this renders 5.4.2 worthless to me. Well, unless someone
patches it in Wonder. :-P I am not sure that I will bother yet.
Isn't there already something in Wonder that should fix this in
ERXWOTextField? Not sure though, just checked briefly in the source.
It looks like ERXWOTextField is similar to the 5.3.3 implementation,
so if you are using Wonder with this patched in as WOTextField then
you won't have problems.
Is the problem just limited to WOTextField? What other diffs are there
between Wonder's and WO5.4.x for this stuff?
with regards,
--
Lachlan Deck
_______________________________________________
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