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. The integration should not force you to write any tapestry specific code to use JSR 303, IMO. It should just work. 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.
On Tue, Oct 13, 2009 at 10:42 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Tue, 13 Oct 2009 17:31:14 -0300, Igor Drobiazko < > igor.drobia...@gmail.com> escreveu: > > If I understood you correctly you suggest the approach of the annotation >> based ValidationConstraintGenerator. Right? >> > > Right. It does not solve the whole problem, but solve it partially and > elegantly. It just reuses the annotations to add the validation constraints > you'd need to add manually. > > > -- > 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 > > -- Best regards, Igor Drobiazko
