I thought that the point was to NOT have to use a property editor, but
rather an xml file
----- Original Message -----
From: "Nick Afshartous" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 9:24 AM
Subject: RE: server-side, java-based validation rules for struts..
>
> Cook, Levi writes:
> > IMHO, expressing rules using first class Java objects *can* be just as
> > flexible as defining rules in an XML file.
> >
> > The analog to changing a value in an XML file is using a property
editor to
> > change values stored in a JavaBean (thus avoiding recompiling). The
upside
> > of this approach is simpler integration with visual editors (simply
> > implement a property editor for your form-bean).
>
> > Ultimately, I feel this is
> > where your less technical people can begin to contribute more
effectivly.
> > The other route requires hand-rolling a visual editor for your XML
scheme
> > and/or having your users learn quite a bit about the intricacies of
your
> > schema.
>
> Thanks Levi for pointing out that a property editor could be used.
> Could one also add new rules and attributes dynamically with a
> property editor ?
>
> Maybe the trickiest part for the users would be to learn the
> syntax for rule expressions. In particular how to refer
> to object attributes within a rule.
> --
>
> Nick
>
>
>
