Re: [5.4-beta-6] Strange behavior with JSR 303 client-side validation and nested beans
Hi Thiago, Switched to beta-16 and yes it is fixed. Thanks Christian 2014-08-29 15:01 GMT+02:00 Thiago H de Paula Figueiredo : > On Fri, 29 Aug 2014 06:41:26 -0300, Christian Dutaret < > cdtapes...@gmail.com> wrote: > > Hi list, >> > > Hi! > > Have you tried one of the latest betas, available in the Apache Maven > staging repository? I recall fixing something like that. > > > I'm using JSR-303 annotations. When validating a field from the page >> class, >> it works as expected, and client-side validation is correctly triggered. >> >> Page.java: >> >>@NotNull >>@Property >>private String firstName; >> >> Page.tml: >> >> >> >> >> >> >> >> >> >> >> >> >> If I submit the form, client-side validation tells me that first name >> should not be empty. >> >> If I try the same, but from a field of a nested bean, then only >> server-side >> validation occurs, not client-side. >> >> Page.java: >> >>@Property >>private Person person = new Person(); >> >> Page.tml: >> >> >> >> >> >> >> >> >> >> >> >> >> Person.java: >> >>@NotNull >>private String firstName; >> >> I don' know if this was working with earlier versions. >> >> Christian >> > > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: [5.4-beta-6] Strange behavior with JSR 303 client-side validation and nested beans
On Fri, 29 Aug 2014 06:41:26 -0300, Christian Dutaret wrote: Hi list, Hi! Have you tried one of the latest betas, available in the Apache Maven staging repository? I recall fixing something like that. I'm using JSR-303 annotations. When validating a field from the page class, it works as expected, and client-side validation is correctly triggered. Page.java: @NotNull @Property private String firstName; Page.tml: If I submit the form, client-side validation tells me that first name should not be empty. If I try the same, but from a field of a nested bean, then only server-side validation occurs, not client-side. Page.java: @Property private Person person = new Person(); Page.tml: Person.java: @NotNull private String firstName; I don' know if this was working with earlier versions. Christian -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
[5.4-beta-6] Strange behavior with JSR 303 client-side validation and nested beans
Hi list, I'm using JSR-303 annotations. When validating a field from the page class, it works as expected, and client-side validation is correctly triggered. Page.java: @NotNull @Property private String firstName; Page.tml: If I submit the form, client-side validation tells me that first name should not be empty. If I try the same, but from a field of a nested bean, then only server-side validation occurs, not client-side. Page.java: @Property private Person person = new Person(); Page.tml: Person.java: @NotNull private String firstName; I don' know if this was working with earlier versions. Christian
