In my case I have validation rules defined in metadata about my
objects. I need to check these rules regardless of whether the object is
being updated via Tapestry, via web services, or via non-presentation code.
It's much more efficient and cleaner to just enforce validation in one place
than it is to create a parallel validation model using tapestry validators.
The one place I use tapestry validator is where I need data type
conversion on forms and/or I need to validate *form* specific things rather
than object specific things. The latter case is fairly rare, but the former
crops up from time to time.
--- Pat
> -----Original Message-----
> From: Sonny Gill [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 04, 2005 9:43 PM
> To: Tapestry users
> Subject: Re: Validation gotcha
>
> Hi John,
>
> I am not a Tapestry user (yet), but from what I have seen, the
> validation in tapestry seems to be among the best in web frameworks.
>
> So I am just curious, what is the motivation for using a separate
> validation framework?
>
> Cheers.
>
> Sonny
>
> Prince John, Bedag wrote:
> > Hi,
> >
> > Here is the setup. I have a preexisting object in the session which is
> > displayed in a form for editing. I am not doing any validation in
> > tapestry because we have a separate validation framework and we collect
> > errors that way, feeding them back into the tapestry system for display.
> >
> > John
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
