I've seen that sort of behavior in 2 common types of cases: 1- An exception occurred, disrupting the Ajax response from even returning (you'll notice it as a type ERROR in the Wicket debug panel)
2- A form validator, required field, or conversion failed, stopping the form from updating underlying models (you would have still seen the onBeforeRender called in this case). You'd notice this behavior if the console had a message about 'unrendered feedback message' -Clint -- Clint Checketts Sent with Sparrow On Thursday, April 28, 2011 at 1:25 PM, Tom Barbaro wrote: > Hi, > > I have several checkboxes in a datatable toolbar that control filtering for > the content rendered in a datatable. When a checkbox is clicked, we add the > datatable to the ajax target, which results in a new query. The dataprovider > doQuery methond is called and returns the correct results. The problem is > the view does not always update. No exceptions occur, the view just does not > update. > > I set a breakpoint in onBeforeRender for the page and it is called when the > view is updated. When the view is not updated it is not called. > > The only clue I have is the number of items in the view for the checkbox I > just unselected is much larger (more than 100x) than the items selected by > the unmodified checkboxes. > > Any ideas what would prevent the updating of the table? > > Tom > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/DataTable-s-view-does-not-always-update-tp3481807p3481807.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 >
