This is precisely my motivation: get Struts out of validation directly, making it easier to re-use commons-validator deeper in the business layer. Struts should be able to utilize validations, but only as a supplement to business logic validation. In my case, my application has multiple interfaces, one being Struts and another Axis. If I convert my application to use commons-validator, I want to make sure I can define validations once and reuse them within both the Struts view layer and deeper in behind the business facade.

Don

Edgar P Dollin wrote:

View based xml for validation of forms, in my view, violates the MVC
paradigm.  Validation is business logic although there is a small benefit to
view based validation for performance reasons.  You have to have validation
code in your business classes, so I don't understand writing a second set of
validations (even if they are only xml) which don't cover the whole range of
validation scenarios.

Additionally, since the tags don't have formatting, I have had to implement
my own tags for all of the formatted fields in order to have an interesting
user interface, i.e. lookups, numbers, phone numbers, dates, etc. which
would obviate the need for simple validations.

Of course there are exceptions, i.e. a completely view based application,
but I haven't had that experience.

Edgar



-----Original Message-----
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 25, 2004 9:00 AM
To: Struts Developers List
Subject: RE: Validator Design Questions


What does "currently constituted" mean?

David

--- Edgar P Dollin <[EMAIL PROTECTED]> wrote:


I for one would never use struts validator as it is currently
constituted
and to be required to use it would cause me to drop using struts. Please
rethink this idea.


Thanks

Edgar



--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.688 / Virus Database: 449 - Release Date: 5/18/2004


--------------------------------------------------------------------- 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]



Reply via email to