Em Tue, 13 Oct 2009 17:53:58 -0300, Igor Drobiazko
<igor.drobia...@gmail.com> escreveu:
The integration of the JSR 303 should not only allow you to use the JSR
annotations like @NotNull but also allow you to use the validation
mechanism provided by the implementation of the JSR like hibernate
validator 4.
I agree 100%.
The integration should not force you to write any tapestry specific code
to use JSR 303, IMO. It should just work.
I agree 100% too.
Furthermore the suggested approach
doesn't work for all annotations provided by JSR 303 because there are
less validators in Tapestry than in the JSR.
That's why I said that approach is a partial solution and some object
validation interface needs to be defined, plus some way to tell Tapestry
what object should be validated. Maybe some Form parameter to tell which
objects should be validated. BeanEditForm already has an object parameter,
so almost no additional code needs to be added.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
