There is a renderHead on behavior: you can use it to contribute JavaScript. Sooner than later, if you want to have complex user interaction at client side, you will end up using extra JavaScript features. There are many examples out there of JavaScript integration with Wicket
On Sat, Oct 26, 2013 at 12:14 PM, meduolis <meduol...@gmail.com> wrote: > When/how should I trigger JS to update attribute? I have never used pure JS > in my Wicket applications. I always try to use Wicket components/behaviors. > > Also, to avoid problem you mentioned about path to child I can pass it as a > parameter which would be static field for both child component and behavior > parameter: > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Elegant-way-to-modify-parent-component-tag-if-child-has-errors-tp4661983p4661985.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
