On Fri, 03 Aug 2012 04:57:02 -0300, mem
wrote:
value has to parsed, probably ending up in the same situation as i'm now
with the production mode. So i guess i'm stuck with adding the css
classes just manually to the fields.
Instead of implementing a ValidationDecorator, you could implemen
That's what i already thought of too, i was just hoping to be wrong.
I tried all kinds of different approaches, a mixin can't really work as it
should be applied to labels automatically and not manually adding a mixin.
Using a worker i would get there but there're issues with the dynamically
create
You are probably running into the fact that Tapestry rewrites your
page/component classes so that there is only one instance of the class used
across all requests. To do this all of the property accesses are
intercepted and replaced with ThreadLocal values. When you are in
development mode tapestry
Hello,
hope this Thread is still alive.
I've used a similar approach to figure out if the label is attached to a
field which renders a required field. The whole thing is a bit complex as
we're using JSR303 annotations on the DTO so i've to get the parameter of
the textField and then evaluate the s
> Unfortunately it seems that it does not help against these error-
> bubbles.
To override the client side you'll need to read tapestry.js and follow some of
what it does. Personally I feel that the error bubbles should not be part of
the T5 core, but an optional example validation module.
I cr
Thanks Thiago, that helped me a lot.
Unfortunately it seems that it does not help against these error-bubbles.
Piero
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h.
