Andreas, This might be a dumb question, but are you sure at the point that the page reloads and re-renders, the object *has* been erased from the database or cache you are utilizing? For example, right after you delete, if you put in some silly/junk code to immediately re-query for that object, it comes back null right?
I'm sure this is an Ajax/model issue, but 1 time it took me 2 days trying to figure out why something "Wasn't deleting" just to find out it was, but my cache was deferring the operation to a few seconds later. So I figured I'd throw that out there just incase. -R On Fri, Jan 29, 2010 at 10:23 AM, Andreas Lüdtke <sam.lued...@t-online.de>wrote: > Hi, > > I have an AjaxFallbackDefaultDataTable on a page and when I delete a row of > the displayed data, I can't get the DataTable to reload and show the > reduced > list. I tried already the following: > > - delete the object (row) in the database > - reload the ISortableDataProvider class I'm using <-- this is actually not > needed, because the object is removed > - AjaxFallbackDefaultDataTable.modelChanged() > > If I refresh the browser window I see that one object is missing in the > list, > but this way I lose the sorting the user has done. > > Am I missing something? How do I bring the AjaxFallbackDefaultDataTable to > reflect the changes? > > Andreas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
