the first link is a bookmarkable link, it recreates the page instance. bind is only called when the behavior is *added* to the component.
link 2 is not a bookmarkable link, it doesnt recreate the page instance so the behavior is not added because a page instance where the behavior has already been added is used, thus no bind call -igor On Mon, May 17, 2010 at 6:22 AM, David Chang <david_q_zh...@yahoo.com> wrote: > I have a top page which has two panel-based components. > > Component 1 implements AbstractBehavior's bind method. > > Component 2 has a wicket Link pointing to a child page. > > When I am at the top page, refresh always gets #bind called. > > When I click the Link in Component 2, the bind method in Component 1 does not > get called. > > Can anybody tell why this happened? > > I am quite puzzled. I am kind of new in wicket. I am using wicket 1.4.8 on > tomcat. > > Regards. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
