true.
in the isVisible impl you could lazy-init cache a transient Boolean until end request where you set it null. setters are evil. egolan74 wrote: > > Yes but ... > isVisible may be triggered several times, while setVisible should only be > called once (say if I do it only once after creating the component). > Usually I prefer the state driven way, but what if the logic has a lot of > overhead? > > > > Jonathan Locke wrote: >> >> >> isVisible is generally better imo because it is state driven. if you >> push instead of pull, the state can get stale. >> >> > > -- View this message in context: http://www.nabble.com/isVisible-vs.-setVisible-tp17860615p17861099.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
