Now the question is whether the validator is a core component?
I don't know what you all define as core but I believe this is a core aspect. How many forms have you built that didn't need validation of at least one required field (if no form fields are required I question the value of the form)?
What are the various options for validation? I see 2 built into Struts: coding a form bean's validate() method and using the validator. What I'm suggesting is that the ActionForm.validate() method use the validator by default.
I just don't see any need to subclass a different ActionForm class to use the validator when it seems that this will become the predominant form of validation.
David
From: Ted Husted <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: Validator Integration
Date: Fri, 25 Oct 2002 13:09:10 -0400
I've been using the Validator for going on three years now, but
I don't think I would ever want to describe it as an integal
part of Struts. Struts provides a validation hotspot, and we
provide the Validation as something people can plug into that
spot. But we want to be very clear that it is only one of many
possible solutions to validation.
We provide direct support for the Validator as a convenience,
but IMHO, it is not part of the true Struts core. (Of course, I
don't consider the tags part of the true Struts core either =:)
I'd also be very cold on amending the struts-config with the
specifics for any optional component, the Validator included.
Ideally, the Validation config could be shared with other
platforms (not just Struts), and should be a standalone file.
As mentioned elsewhere, there were two classes since some
people (or maybe one person) wanted to key on the action path
rather than the action attribute. But if we were patch this to
use a switch, mores the better.
-Ted.
10/25/2002 10:34:52 AM, David Graham <[EMAIL PROTECTED]>
wrote:
>It struck me the other day that the validator could be further
integrated
>into struts. I'm not sure about my ideas so I want to get
your thoughts. y
>Why should people need to subclass ValidatorActionForm instead
of ActionForm
>to use the validator? What forms have you built that didn't
need
>validation?
>
>My idea is that the ValidatorActionForm and ValidatorForm (why
are there 2?)
>behavior should be included in ActionForm and have those
classes removed. I
>think this will maintain backward compatibility because if the
developer
>hasn't defined any validation rules for a form then we could
return null
>from validate().
>
>Further, we could include validator configuration tags in
struts-config.xml
>instead of using a plugin. This would signify that validator
is an integral
>piece of struts that most people want to use (which I believe
they do).
>
>This is probably a post 1.1 idea but I thought I'd throw it
out here.
>What do you think?
>
>David
>
>
>
>
>
>______________________________________________________________
___
>Unlimited Internet access -- and 2 months free! Try MSN.
>http://resourcecenter.msn.com/access/plans/2monthsfree.asp
>
>
>--
>To unsubscribe, e-mail: <mailto:struts-dev-
[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:struts-dev-
[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
