cant you just write a validator class that looks up if its valid in a database and then add it to your config file and use that? how is that limiting??
On 2/1/06, Aj Gregory <[EMAIL PROTECTED]> wrote: > > It seems very limiting that you can only specify a class for > "tapestry.form.translator.Translators " and > "tapestry.form.validator.Validators" configuration points. > > I'd really like an option to setup a service id or better yet an object > so I can create more interesting translators and validators which depend > on other services. For example if I wanted a validator which takes the > contents of an input field and looks up if it's valid by making a > database call. > > Has anybody else tried to get around this limitation? > > -Aj > < > http://jakarta.apache.org/tapestry/tapestry/hivedocs/config/tapestry.valid.Validators.html > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
