A few initial comments:
* As we have tapestry-hibernate-core, shouldn't it be named
tapestry-bean-validator?
* Why don't we add some object validation service to Tapestry-IoC and have
tapestry-beanvalidator implement it? This way, non-web code can also use
the validation code.
* I haven't read almost anything about JSR 303 yet, but does
tapestry-beanvalidator implement cross-property validation like
@AssertTrue or @AssertFalse?
* Is it the whole code or this commit is just a partial one?
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
