On Tue, Oct 13, 2009 at 9:50 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote:
> Em Tue, 13 Oct 2009 16:46:56 -0300, Igor Drobiazko < > igor.drobia...@gmail.com> escreveu: > > The integration of the JSR 303 is difficult without to break the >> compatibility of the API beacuse the Tapestry validation mechanism is only >> aware of a >> value being validated. >> > > One thing that is easy to do is to provide Validator implementations based > on annotations (@NotNull -> required, @Min(n) -> min=n), etc. > I would not do it this way. Just image a bean which is used in several projects (rich clients and tapestry apps). You want your validation work same in all your apps. > We'll probably need to define something like an ObjectValidator<T> > interface to provide validation of whole objects, not only invividual > properties. I'll start the discussion in the dev list. > > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Best regards, Igor Drobiazko
