Em Tue, 13 Oct 2009 18:22:51 -0300, Igor Drobiazko
escreveu:
In this case the JSR 303 validation would take place inside the form
component (not it is distributed across several fields).
IMHO, it should be distributed across fields too, using
ValidationConstraintGenererator, so Tapestry c
On Tue, Oct 13, 2009 at 11:03 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> 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 al
Em Tue, 13 Oct 2009 17:53:58 -0300, Igor Drobiazko
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
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
Em Tue, 13 Oct 2009 17:31:14 -0300, Igor Drobiazko
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 annotation
If I understood you correctly you suggest the approach of the annotation
based ValidationConstraintGenerator. Right?
On Tue, Oct 13, 2009 at 10:14 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> Em Tue, 13 Oct 2009 16:59:35 -0300, Igor Drobiazko <
> igor.drobia...@gmail.com> escr
Em Tue, 13 Oct 2009 16:59:35 -0300, Igor Drobiazko
escreveu:
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 clien
As already mentioned in the user's mailing list the integration of the JSR
303 is problematic because the Tapestry validation mechanism is only aware
of the value being validated. There is no chance to get the page or bean
whose property is validated. I already started the integration of the JSR
30
