> So the question is, what if I have those validation strings (maxLength=5,minLength=2..etc) in an independant string ? Because I intend to have this information in a database (label, name\id, validation rules).
You could provide a DatabaseConstraintGenerator in a similar way to how Tapestry provides a MessagesConstraintGenerator. 1. In your AppModule, decorate the "FieldValidatorDefaultSource" service to push and pop any contextual information that you will need to lookup your database config (most likely the fieldName and the pageName). 2. Implement a ValidationConstraintGenerator which uses Environment.peek() to lookup the context and get the constraints for a field 3. Contribute your DatabaseConstraintGenerator to the "ValidationConstraintGenerator" service. -- View this message in context: http://tapestry.1045711.n5.nabble.com/t5-3-Using-a-map-object-with-BeanEditor-tp5712589p5712781.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
