That's another one of my concerns. I don't know how much JSF will replace the need for this. If it doesn't, then I think this is the way to go.

David






From: Eddie Bush <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: Validator Integration
Date: Fri, 25 Oct 2002 15:51:11 -0500

Sounds cool - sounds like a pretty substantial change though. Maybe we could table it for now and pick it up for 2.0.x? Of course, at that point, we'll have JSF coming in (most likely) and it will bring it's own pluggable field validators ... and what else will we need?

David Graham wrote:

Actually, I think that's what I really wanted without knowing it :-). Struts already provides pluggable RequestProcessors for the ActionServlet, maybe it should allow pluggable Validators for ActionForms. This way, we don't mandate the use of the commons validator or anything else, we just allow different implementations.

My first thought is that there could be a Validator (or ActionFormValidator, etc.) interface with a method like:

ActionErrors validate(ActionForm form, any other needed params);

We could provide a compliant implementation class for the commons validator. Just like RequestProcessor, the validator implementation could be configured in struts-config.xml.

I think this addresses Ted's concerns of mandating the use of certain technologies because it creates a pluggable service layer.

What do you think?

David

--
Eddie Bush




--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>

_________________________________________________________________
Surf the Web without missing calls! Get MSN Broadband. http://resourcecenter.msn.com/access/plans/freeactivation.asp


--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>

Reply via email to