• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: What is the best way to handle invalid values from a WOTextField?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Ralf Schuchardt <email@hidden>
  • Date: Tue, 17 Jun 2008 22:49:26 +0200


Am 17.06.2008 um 20:25 schrieb Chuck Hill:


On Jun 17, 2008, at 11:09 AM, Ralf Schuchardt wrote:


Am 17.06.2008 um 19:32 schrieb Chuck Hill:


On Jun 17, 2008, at 10:04 AM, Ralf Schuchardt wrote:

Hi,

in the past (until WO 5.4) I often have used a WOTextField with a formatter to prevent errors like this:

"java.lang.IllegalArgumentException: While trying to invoke the set method "public void com.cx.harow.eos._ArztFolgedokLeistung $StorageClass.setAnzahl(java.lang.Short)" on an object of type com.cx.harow.arzt.dokumente.ArztFolgedokumentationContext $TempFolgedokLeistung we received an argument of type java.lang.String. This often happens if you forget to use a formatter."

When a value was invalid the formatter did not set an invalid value in my objects.

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.

WOTextField:

formatter
[...]

If a user enters an “unformattable” value, WOTextField passes the invalid value through, allowing you to send back an error page that shows the invalid value.

[...]

Uh oh. Are you saying that it no longer calls

void
validationFailedWithException(Throwable t, Object value, String keyPath)
Called when an Enterprise Object or formatter failed validation during an assignment.


When the format operation fails? That is a bug. Or a totally unacceptable API change.


In theory it does. But before it reaches this part it tries to push the invalid string into the binding and this may fail.


Ralf _______________________________________________ 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
References: 
 >What is the best way to handle invalid values from a WOTextField? (From: Ralf Schuchardt <email@hidden>)
 >Re: What is the best way to handle invalid values from a WOTextField? (From: Chuck Hill <email@hidden>)
 >Re: What is the best way to handle invalid values from a WOTextField? (From: Ralf Schuchardt <email@hidden>)
 >Re: What is the best way to handle invalid values from a WOTextField? (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: More efficient web service choice
  • Next by Date: Ahem. Do Not Run This Script
  • Previous by thread: Re: What is the best way to handle invalid values from a WOTextField?
  • Next by thread: Re: What is the best way to handle invalid values from a WOTextField?
  • Index(es):
    • Date
    • Thread