Only happens if we start with an empty grid i.e. first time data entry. GWT WindowStatus (WS) cache also ignores further changes in JavaClient side.
If New record or Undo action done in an empty new window in GWT, will leave shadow records in Grid (upper panel of ContentView) as they do not exist in JavaClient. If then a new record is created in Javaclient it does not show up in GWT UI, perhaps the WindowStatus (WS) cache should think about it.
When JavaClient creates the new record first, it will show up when first time open in GWT UI, and when GWT udpates that record or create more records, it shows in JavaClient. But edit in JavaClient will not show up in GWT, when reopen window or even relogin. The Tomcat server has to restart to make that refresh. This proves that i.e. WS is not checking for record lock and still keeps its own cache even after reopen. In other words, GWT only fetches one-time during first time record access from JavaClient then GWT can update one way back.