Awesome, works beautifully! This solves one of the biggest Wicket headaches
for our form-heavy application. Components no longer have to worry about
what to render when forms have errors, or how to clear those errors on
success. It's even more magical than the automatic AJAX feedback rendering.
:)
your attachment didnt make it through :(
maybe put it on our wiki.
thanks,
-igor
On Thu, Jul 21, 2011 at 12:00 PM, Dan Retzlaff dretzl...@gmail.com wrote:
Awesome, works beautifully! This solves one of the biggest Wicket headaches
for our form-heavy application. Components no longer have to
No problem, it's the least I can do. :)
https://cwiki.apache.org/confluence/display/WICKET/Automatic+styling+of+form+errors
On Thu, Jul 21, 2011 at 12:02 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
your attachment didnt make it through :(
maybe put it on our wiki.
thanks,
-igor
On
Hey all,
I want a low-interference approach to adding CSS class attributes to form
components and their labels when they have associated errors. Igor's *
Cookbook* suggests a behavior, but leaves the automation as something done
during page construction. We have too many AJAX modals and panel
no worries, the cookbook has your back!
look in this recipe: Providing Ajax feedback automatically
have your temporary behavior implement a tagging interface. then in
the ajax request target listener look for all components that have a
behavior with this tagging interface, and if they do add it
Hey it's the man himself. :)
We already use the automatic AJAX feedback recipe (thanks for that), but I'm
not sure how that solves the problem at hand. I only add the temporary
behaviors in myIComponentOnBeforeRenderListener, and that only gets called
if the component's *already* been added to
On Wed, Jul 20, 2011 at 9:11 PM, Dan Retzlaff dretzl...@gmail.com wrote:
Hey it's the man himself. :)
We already use the automatic AJAX feedback recipe (thanks for that), but I'm
not sure how that solves the problem at hand. I only add the temporary
behaviors in
