Details
Bug
Major
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
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Fix Version/s | 2.0-Beta2 [ 10242 ] | |
| Assignee Priority | P2 | |
| Assignee | Mircea Toma [ mircea.toma ] |
| Link | This issue blocks ICE-5779 [ ICE-5779 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 2.0.0 [ 10230 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee Priority | P2 |