On Fri, 12 Aug 2011 09:13:22 -0300, Igor Drobiazko
wrote:
The tapestry-beanvalidator module doesn't has a dependency to any
implementation of the JSR 303. The app developer needs to choose one and
drop it on the classpath. So, the dependency to org.apache.bval.bundle
is correct.
Thanks f
On Fri, Aug 12, 2011 at 1:45 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
>
>
> You don't need these dependencies, as Tapestry-BeanValidator already uses
> Hibernate Validator 4 for that.
>
>
The tapestry-beanvalidator module doesn't has a dependency to any
implementation of the J
You placed the annotations on the card bean, but you are passing the page
instance to the form's validate parameter (validate="this"). That's why the
validator doesn't see any validation constrains.
On Fri, Aug 12, 2011 at 9:26 AM, kleanthis wrote:
> Hello all. I am facing a problem and have not
On Fri, 12 Aug 2011 06:19:31 -0300, nillehammer
wrote:
Hi kleanthis,
try t:value="card.cardId" instead of value="card.cardId".
I prefer to use the t: prefix in any parameter which isn't a normal
attribute of the HTML tag used, but it won't make any difference for
Tapestry.
--
Thiago
On Fri, 12 Aug 2011 04:26:19 -0300, kleanthis wrote:
Hello all.
Hi!
I am facing a problem and have not been able to find a solution. I want
to integrate JSR-303 with tapestry 2.5.6.
The problem is that some of my beans/entities come from a diferent domain
model, so i cannot annotate them
I changed value to t:value and nothing changed. It seems tapestry cannot
create the necessary validators for the annotations. Removed @NotEampty from
the variable. It was left there while expirementing. Any other ideas?
Did anyone got this to work at least?
-
Do not confuse motion for action.
Hi kleanthis,
try t:value="card.cardId" instead of value="card.cardId". And the annotation
@NotEmpty is not necessary in my opinion.
-
http://www.winfonet.eu
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-and-JSR-303-tp4692368p4692609.html
Sent from the Tap
