Hello,
It looks like RestDataSource is completely ignoring invalidateCache flag. I used the test project from wiki https://isomorphic.atlassian.net/wik...?pageId=524942 with invalidateCache flag added to the add request, see the attachment. Once user hits Add button a new record gets added as expected, but since invalidateCache is set to true in the response, a new fetch should be issued by the grid. The grid is not refreshing though. Both 3.1 and 4.0d behave the same.
RestDataSource documentation mentions that "The request and response formats used by the RestDataSource allow for many of the available features of Smart GWT's databinding system to be used, including data paging, searching & sorting, long transactions, automatic cache sync, relogin and queuing." Does it imply that invalidateCache should be supported?
It looks like RestDataSource is completely ignoring invalidateCache flag. I used the test project from wiki https://isomorphic.atlassian.net/wik...?pageId=524942 with invalidateCache flag added to the add request, see the attachment. Once user hits Add button a new record gets added as expected, but since invalidateCache is set to true in the response, a new fetch should be issued by the grid. The grid is not refreshing though. Both 3.1 and 4.0d behave the same.
RestDataSource documentation mentions that "The request and response formats used by the RestDataSource allow for many of the available features of Smart GWT's databinding system to be used, including data paging, searching & sorting, long transactions, automatic cache sync, relogin and queuing." Does it imply that invalidateCache should be supported?
Comment