• 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: Validation messages
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Validation messages


  • Subject: Re: Validation messages
  • From: Tom Woteki <email@hidden>
  • Date: Thu, 8 Jul 2004 20:49:34 -0400

One approach that is not "light weight" but that will pay large dividends, particularly if you amortize the effort over a large application or or over several projects, is to employ the Validity framework that gammastream contributed to Project Wonder.
See http://wonder.sourceforge.net/


With this framework you can replace, or bypass, EOModel constraint checking and additionally provide any number of cascading validity checks on each attribute of an entity. The specification of which validity checks to perform and the failure messages that should be returned are stored in your EOModel bundle. This very brief description does not do justice to the utility of the framework.

It is possible, and not particularly difficult, to separate the Validity framework from the rest of Project Wonder, which is a significantly larger proposition to take on. Based on the last version I checked out, you will also have to update a very small portion of the Validity code if you want to avoid its use of deprecated methods in Apple's WO or EO frameworks.

Others can and have commented on the value of Project Wonder. I have not absorbed that. But investing in the Validity framework has paid off handsomely for me.

Tom


On Jul 8, 2004, at 6:57 AM, Clark, Igor wrote:

I posted a question about this a while ago but I can't find it by searching
on the omni list or on WODev, and I remember it being slightly inconclusive
anyway. Hopefully someone will be able to help out!


I have a simple validation mechanism in place for form components using
validationFailedWithKey and a validation dictionary as suggested in Malcolm
Crawford's Stepwise article. I'm into IS testing now and most of the 'bugs'
<snip>

"For Enterprise Objects, these methods are called after any constraints in
the EOModel have been checked."


<snip>

Any ideas?
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: Validation messages
      • From: Anjo Krank <email@hidden>
References: 
 >Validation messages (From: "Clark, Igor" <email@hidden>)

  • Prev by Date: Re: D2JC Client-Side Application...
  • Next by Date: Searching NSArray of EO objects for key value
  • Previous by thread: Validation messages
  • Next by thread: Re: Validation messages
  • Index(es):
    • Date
    • Thread