On Jan 23, 2008 1:12 AM, Dmitry Kandalov <[EMAIL PROTECTED]> wrote: > On Wednesday 23 January 2008 12:55:17 Martijn Lindhout wrote: > > I like that one with the ResourceReference. What about providing a setter > > on the component, so that no subclassing is needed? > > IMO setter or constructor parameter should be ok, though Wicket classes use > getters (probably to reduce session size?).
Yep, we often work with overridable methods instead of properties because it saves memory. Probably not something you have to worry too much about when you create your custom components, but especially for the Wicket basic components, this can make quite the difference. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
