Excellent. Thank you (and Devin and Vince) for the quick response. I'd
rather do things one step at a time, but I wasn't quite sure about this
one!
Thanks again.
Susan
"V. Cekvenich" <[EMAIL PROTECTED]>
Sent by: news <[EMAIL PROTECTED]>
10/24/2002 02:04 PM
Please respond to "Struts Users Mailing List"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Validator later rather than sooner?
If you do iterative development I add Validation in late iterations.
.V
Richards, Devin N (Devin) wrote:
> Since the validator classes extend the standard struts classes, I would
get everything working correctly and then add the validator in after. We
did this and it worked well (except for the current bug of the validator
not supporting multiple resource bundles.)
>
> -Devin
>
>
> -----Original Message-----
> From: Susan Bradeen [mailto:SusanB@;softlanding.com]
> Sent: Thursday, October 24, 2002 1:50 PM
> To: [EMAIL PROTECTED]
> Subject: Validator later rather than sooner?
>
>
> Is it general practice, or recommended, to develop a Struts application
> using the Action/ActionForm classes first (getting everything working
> properly) and later switch to the Validator classes, OR to use the
> Validator classes (implementing validation) right from the beginning?
>
> I have done a little with form validation, but not enough to know if I
> will get myself in trouble by waiting and "switching" class sets later
on.
>
> Thanks,
> Susan Bradeen
>
> --
> To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
