On Mon, 16 Jun 2008, Johan Compagner wrote: > Calls are synced but they can be in the wait for each other and if > then the first changes the component structure then the other that is > already waiting comes in then it cant find it anymore. But this call > should just be ignored as far as i know
I don't think it is, at least in 1.3.4? > > On Sun, Jun 15, 2008 at 7:46 PM, Cristi Manole <[EMAIL PROTECTED]> > > wrote: > >> I have a table with a drop down in one of the columns. This table gets > >> refreshed every 10 seconds through Ajax. > >> > >> I did some testing and it seams I get the error when I'm trying to change > >> the content of the drop down (which gets posted through Ajax) exactly when > >> the table gets refreshed. So it fails with that error being caused by the > >> fact that Wicket cannot find a page for the drop down component. So are you updating also the dropdown via ajax? If your table (or its row) is a repeater that creates its items again on rendering, this might cause the problem, because the original dropdown would not be in the component hierarchy anymore. So here an item reuse strategy as Maurice suggested might help. Also you could check that the dropdown is still on the page before adding it to AjaxRequestTarget, or consider whether you have to add it separately at all if the whole table gets repainted pretty frequently anywway. It should be easy enough to find out when new items are created (e.g. with Thread.dumpStack() in newItem). Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
