The 2nd stack trace (you can see the time stamps) was done on request via a menu button minutes after the transition. So I don't think it was a race condition, if that is what you are thinking?
The 1st stack trace happens when
the resultTree.setOpenState(treeGrid.getOpenState()) is executed. I see the log output 'new ResultTree added to treeGrid' after the stack trace in the log.
Then minutes later, I manually initiate the TreeGrid.invalidateCache() call which triggers the 2nd stack trace above.
Do you still think it is a timing issue? So we loose the cache by replacing the ResultTree with a new one? Or was that more related to aa timing issue as well?
The 1st stack trace happens when
Code:
ResultTree resultTree = new ResultTree(); resultTree.setData(objects); resultTree.setDataSource(treeGrid.getDataSource()); --> resultTree.setOpenState(treeGrid.getOpenState()); treeGrid.setData(resultTree); GWT.log("new ResultTree added to treeGrid.");
Then minutes later, I manually initiate the TreeGrid.invalidateCache() call which triggers the 2nd stack trace above.
Do you still think it is a timing issue? So we loose the cache by replacing the ResultTree with a new one? Or was that more related to aa timing issue as well?
Comment