Why does CellTable hold on to AsyncDataProvider instances ?

2011-02-11 Thread will0
Hi All I've got a fairly standard gwt 2.1.1 setup, a CellTable which is controlled by an Activity. Each time the Activity is instantiated on a place change, this creates a new AsyncDataProvider. It appears the CellTable keeps a reference to _all_ the AsyncDataProviders it has ever come

Re: Why does CellTable hold on to AsyncDataProvider instances ?

2011-02-11 Thread John LaBanca
You have to remove the cell table from the AsyncDataProvider when your activity is stopped or cancelled: AsyncDataProvider.removeDataDisplay(cellTable); The way its implemented, AsyncDataProvider adds a RangeChangeHandler to the cellTable. How else would the CellTable know that the

Re: Why does CellTable hold on to AsyncDataProvider instances ?

2011-02-11 Thread will0
Great, thanks, that's what I was looking for. Just this wasn't immediately obvious to me, perhaps because it wasn't mentioned in the docs: http://code.google.com/webtoolkit/doc/latest/DevGuideUiCellWidgets.html#data-provider Best, Will -- You received this message because you are subscribed