Details
Description
In testing the Auction example with MyFaces, I noticed that when the session expired, I was receiving the proper response from the push requests:
<?xml version='1.0' encoding='UTF-8'?>
<partial-response>
<error>
<error-name>class org.icefaces.application.SessionExpiredException</error-name>
<error-message><![CDATA[Session has expired]]></error-message>
</error>
</partial-response>
but it was not popping up a notification on the client nor was it shutting down push. Push would keep running and returning the SessionExpiredException over and over.
I set some breakpoints at various points in the bridge.js code to see where it might be breaking down but it doesn't appear that the following function is being called at all:
function filterICEfacesEvents(f) {...
which suggests that the callback is not being called for some reason:
jsf.ajax.addOnError(filterICEfacesEvents(submitErrorBroadcaster(networkErrorListeners, serverErrorListeners)));
<?xml version='1.0' encoding='UTF-8'?>
<partial-response>
<error>
<error-name>class org.icefaces.application.SessionExpiredException</error-name>
<error-message><![CDATA[Session has expired]]></error-message>
</error>
</partial-response>
but it was not popping up a notification on the client nor was it shutting down push. Push would keep running and returning the SessionExpiredException over and over.
I set some breakpoints at various points in the bridge.js code to see where it might be breaking down but it doesn't appear that the following function is being called at all:
function filterICEfacesEvents(f) {...
which suggests that the callback is not being called for some reason:
jsf.ajax.addOnError(filterICEfacesEvents(submitErrorBroadcaster(networkErrorListeners, serverErrorListeners)));
Issue Links
- blocks
-
ICE-8506 CLONE -Session Expired responses received but not displayed.
- Closed
This is a regression as it does not happen in the 2.1 beta release - the Session Expiry dialog popups up properly.