It depends on what your behavior does. Obviously if your behavior holds a
reference to the component that is passed in to bind(Component), you can not
use a shared behavior.
Anyway, it's really based on that particular behavior. Safest bet is to
create one for each so you don't have a hard-to-tr
> hey, what is the prefered approach?
Try using an IVisitor you pass to visitChildren() in the outermost component.
- Tor Iver
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-
hey, what is the prefered approach?
thanks
joe
On Wed, May 19, 2010 at 7:12 AM, Joe Fawzy wrote:
> Hi
> i have a large number of components in a page that i have to add the same
> behaviour
> should i use the same instance for all or instansiate one for every
> component(that's what i am current
Hi
i have a large number of components in a page that i have to add the same
behaviour
should i use the same instance for all or instansiate one for every
component(that's what i am currently doing);
thanks
Joe
