first, the validators parameter is a normal parameter, just construct
your own validator - just the way you like it to be, add a property
accessor method to it, and use ognl:myValidator instead of validators:...
Then again, if you want to use a bean, you can still easily combine it
using "validators:$byBeanName,required"
you can wire services to your bean by injecting them to your class and
setting the bean's properties -
so there are actually quite some ways to do what you want - (almost) no
limitations :)
Cheers,
Ron
Aj Gregory 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
