Re: Wonder Validity or Custom Validation
Re: Wonder Validity or Custom Validation
- Subject: Re: Wonder Validity or Custom Validation
- From: Gustavo Pizano <email@hidden>
- Date: Thu, 14 May 2009 14:38:52 +0200
LOL... thanks for the feeling. Im serious about WO, but I can't travel that easily to the States. Os my only source of info its PWO, apple docs, and the list... oh yes and my motivation to keep going.
On Thu, May 14, 2009 at 2:20 PM, David LeBer
<email@hidden> wrote:
On 14-May-09, at 6:24 AM, Pascal Robert wrote:
Le 09-05-14 à 05:24, Timo Hoepfner a écrit :
Hi Gustavo,
nevertheless, if you can wait a few weeks, I'd wait for the new validation framework that Chuck announces in his WOWODC session description.
There is another validation framework, that wasn't mentioned yet: http://code.google.com/p/houdah-webobjects-frameworks/wiki/HoudahEOValidation
... which was explained at WOWODC 2008 :-)
Timo
Am 14.05.2009 um 10:41 schrieb Gustavo Pizano:
I wish I can... :( . Im in Slovakia... and can't go the WOWODC. I missing all the good stuff....
Maybe I will be buying the videos after the WOWODC.. if there are gonna be posted.
On Thu, May 14, 2009 at 10:22 AM, Timo Hoepfner <email@hidden> wrote:
Maybe visiting WOWODC would make your life much easier:
--- snip ---
EOF Validation: The Next Generation
Speaker : Chuck Hill
Validation is one of the least satisfactory parts of WebObjects. It shows signs of promise and of abandonment, like a prototype left uncompleted. We will start with a survey of the state of validation in WebObjects and the extensions found in Wonder's core ERExtensions frameworks; the seldom used Validity framework; and in the GVC EOFValidation framework. We will then dive in to take a look at EOF validation "deep under the covers" focusing on the mechanics of how it can be extended. We will then define the functionality that will make the next generation of validation for WebObjects and examine an implementation.
With a validation roadmap in place and a highly functional validation base available, we will turn our attention to the WOComponent presentation layer. Here, too, validation handling leaves much to be desired and the functionality is not clear. We will look at the often ignored validation handling in WOComponent and how it quickly breaks down. We separate WOComponents into two categories, Pages and PageComponents, and get them to co-operate in handling validation. The result will be a page that can orchestrate validation handling, including handling optimistic locking exceptions equally whether they occur within one EOF stack or across instances. This will allow us to create drop-in components that can handle their own validation in a co-operative fashion with the page. As with validation, a functional, documented foundation will be supplied.
In this session you will learn:
how WebObjects validation is implemented
how WebObjects validation can be extended
how to make working with validation easier
how validation handling was intended to work with WOComponent
how to bring working validation handling to WOComponent
how to detect optimistic locking exceptions within one EOF stack
how to handle all optimistic locking exceptions
how to use inheritance and composition to make validation handling and presentation painless
how to contribute to the future of EOF validation
The result of this session will be the release of two new frameworks for WebObjects validation (one for the EOF layer and one for the WOComponent presentation layer). These frameworks will be written to be independent of other frameworks (including Project Wonder) so everyone will be able to use and benefit from them. These frameworks will be functional, but there will be areas where additional functionality can be added (such as support for additional databases). The intention is that these will get completed by others in the community.
--- snip ---
>From http://www.wocommunity.org/wowodc09/west/topics.html#validation
Timo
Am 14.05.2009 um 09:36 schrieb Gustavo Pizano:
HEllo, after reading, the Validation Chapter on the PWO, at the end Chick mention validity as an alternative... now, Im planing and designing the whole implementation and strategy to follow. prior start coding.. I want to ask if using Validity will make my life easier,.. or in the other hadnt I should use the "Practical Solution" that they mention on the book... Pros. Cons... Im still little confused with the subject, but I think I understand most of the "stack call" that happens in the insights of the EOF when validation occurs.
Thanks to PWO and the EOF PG
Gustavo
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
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
_______________________________________________
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