I am facing a similar issue, where after refreshing a page section (i.e. DataView-Container containing AjaxLinks in each item) using ajax, the AjaxPostCallbackHandler (which is registered on the initial page-load) is not invoked anymore, which as Young mentioned is due to the fact that wicket-ajax.js is reloaded..and the registered-callback is wiped out...
Any suggestions to resolve this.. MYoung wrote: > > I filed a bug report: https://issues.apache.org/jira/browse/WICKET-1572 > > This bug is so unfathomable, there is got to be some psychic being > involve. > > > On Wed, May 21, 2008 at 2:32 AM, TonyVegas <[EMAIL PROTECTED]> > wrote: > >> >> *revive zombie* >> >> has any simple solution been found? I am dealing with the same issue. >> >> >> >> RobinShine wrote: >> > >> > Hi Matt, >> > >> > Thanks for your quick answer. Although in this simple case, it is >> enough >> > to only update the count label. However in my application, it is >> > necessary to update the whole region including the component initiating >> > the ajax action. One scenario is that I've written a treetable >> component >> > based on table structure, and it encloses ajax links used to >> > expand/collpase tree nodes. In the event handler of thse links, I >> modify >> > tree structure to satisfy node expanding/collapsing, and add the whole >> > treetable component to the ajax request target for simplicity reason. >> > >> > From your words, it seems that it is not safe to use Wicket Ajax this >> way. >> > However, my application uses this "pattern" extensively. Are there any >> > other approaches for my scenario? >> > >> > Regards. >> > Robin >> > >> > Matthew Young <[EMAIL PROTECTED]> wrote: The problem is you are ajax >> > updating this whole thing including the nested >> > ajaxlink: >> > >> > >> > >> > >> > link >> > >> > >> > >> > >> > it causes the wicket-ajax js stuff header contributed everytime the >> link >> > is >> > clicked. Open the ajax debug window to see. This re-init wipe out the >> > postcallhandler install on page load so there is nothing there to call >> > once >> > the link is clicked. >> > >> > I cannot explain why you need to close and re-open the browser for this >> to >> > happen. It shouldn't work at all. I'm sure Matej and Igor can explain. >> > >> > Change your page to this and only ajax update the "count" then you have >> no >> > problem: >> > >> > >> > >> > >> > >> > >> > >> > link >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Ajax-postcall-handler-does-not-get-called-every-time-tp16659218p17359455.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] >> >> > > -- View this message in context: http://www.nabble.com/Ajax-postcall-handler-does-not-get-called-every-time-tp16659218p18475573.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]
