My medium term plan is to make Tapestry smarter about the Hibernate
annotations; so it will see @NotBlank and @Email and set up the
correct Tapestry validations for those, as if
@Validate("required,email") were present, in addition to any actual
@Validate annotation.
On Thu, Oct 30, 2008 at 5:23 A
Em Thu, 30 Oct 2008 14:34:02 -0300, Francisco Manzano
<[EMAIL PROTECTED]> escreveu:
Why don't you use t:validate in the template?
Do you have a lot of templates that USE this entity ?
Example:
t:validate="required" />
You could also create a simple component with the form that edits your
e
James Sherwood wrote:
Hello,
I have the reverse engineering working correctly but I wish to modify it a
bit.
Tapestry requires and @Validate("required") annotation in front of the
variables of the class that are required for global validation. (Unless
there is a way to do global validatio
Em Thu, 30 Oct 2008 09:23:26 -0300, James Sherwood
<[EMAIL PROTECTED]> escreveu:
Tapestry requires and @Validate("required") annotation in front of the
variables of the class that are required for global validation. (Unless
there is a way to do global validation without using @validate in the
Hello,
I have the reverse engineering working correctly but I wish to modify it a
bit.
Tapestry requires and @Validate("required") annotation in front of the
variables of the class that are required for global validation. (Unless
there is a way to do global validation without using @validate
