Details
Description
A number of cases have been resolved related to handling of session expiration (see ICE-5980, ICE-5997, ICE-6004, ICE-6005). Now, under most proper conditions, a custom SessionExpiredException will be thrown and displayed on the client. This works when ICEpush is present and will display in all views related to the expired session.
There are a still some outstanding behaviours related to the bridge related to proper handling of the exception.
- the Session Expired dialog appears in compat mode even if a connection status component is present (this blocks ICE-5779)
- it appears that, if push is running, it continues to run even after receiving the session expired response
There are a still some outstanding behaviours related to the bridge related to proper handling of the exception.
- the Session Expired dialog appears in compat mode even if a connection status component is present (this blocks ICE-5779)
- it appears that, if push is running, it continues to run even after receiving the session expired response
The test case appears to work properly now. The only issue that I see is that the Session Expired popup gets displayed even though the connection status component is present.