My intent was to mention that property editor's are an option, quite
possibly an option I would employ.
Another option I see as being quite reasonable is storing configuration
info. in an DBMS, so that I can edit through a web browser. This might very
well take the form of a date validating regex or MAX_VAL_INCLUSIVE,
MIN_VAL_EXCLUSIVE boundaries for a numeric field on my form.
Main point being, a validation **framework**, ultimately shouln't care where
or how I choose to specify configution values. Its only concern should be
invoking the interfaces it defines and I implement and register.
-- Levi
> -----Original Message-----
> From: Jonathan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 25, 2001 9:18 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: server-side, java-based validation rules for struts..
>
>
> I thought that the point was to NOT have to use a property editor, but
> rather an xml file
