The nicest way I can think of to solve: http://www.nabble.com/Reach-into-a-component-to-change-XML-attribute-tf4527906.html
Would be to override add, removeAll, remove etc to manage AttributeModifier when the children change rather than every time the components render etc... So I'm not being won over by the final thing since I'd like them gone for my auto-dirty, first/last class attribute and so I can keep using onClick and onSubmit... If I'm hitting an imaginery brick wall then I'd be delighted to be shown the light. Cheers Sam Eelco Hillenius wrote: > > On 9/26/07, Johan Compagner <[EMAIL PROTECTED]> wrote: >> but this discussion is not just about getter/setters (i don't care about >> those) >> but also for add and remove.. then we are getting into some other stuff > > Yes. Getters/ setters are less tricky. Though I'm still not breaking > in sweat when I imagine removing final on add and remove. > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/auto-dirty-and-widget-factory-tf4421187.html#a12940572 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
