actually my suggestion is not good for every usecase ,it's not good in the context where you want to preserve old state of B so check if it's ok for you else get into B , see what can be moved in onbeforerender/onconfigure,make your models dynamic..
On Mon, Apr 22, 2013 at 11:13 AM, vineet semwal <vineetsemwa...@gmail.com>wrote: > oninitialize is only called once like constructor,the only advantage is > called after component is added to page. > the easiest way for you without making any change in B will be replacing > the old instance of B with new one see Component#replacewith(newcomponent) > > > On Sun, Apr 21, 2013 at 2:46 PM, souvikbhattacharyas < > souvikbhattachar...@gmail.com> wrote: > >> I am new to wicket and stuck in a Panel refresh problem with >> AjaxRequestTarget. I am clarifying my scenario below. >> >> In the Ui I have a Panel (A) which contains another Panel (B) and B >> contains >> some buttons and tables. I Panel A, I have a Event which will refresh My >> Panel B (Mainly the table in Panel B) with AjaxRequestTarget. On event I >> am >> adding Panel B in my AjaxRequestTarget.add() but it's not calling my >> initialize method in Panel B. So, Panel B is not refreshing properly. >> >> It's a existing code so, can't move the event to Panel B. So, need to do >> something from Panel A itself. >> >> Any help is appreciable >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Panel-resfresh-with-AjaxRequestTarget-tp4658145.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > regards, > > Vineet Semwal > -- regards, Vineet Semwal
