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
Activity
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 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #22418 | Fri Sep 24 09:50:17 MDT 2010 | mircea.toma | |
Files Changed | ||||
![]() ![]() ![]() |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #22479 | Thu Sep 30 13:59:40 MDT 2010 | mircea.toma | |
Files Changed | ||||
![]() ![]() |
Fix Version/s | 2.0.0 [ 10230 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P2 |
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.