Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 388280

Summary: UICallBack should trigger new UI request in case of session timeout
Product: [RT] RAP Reporter: Ralf Sternberg <rsternberg>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: elias
Version: 1.5   
Target Milestone: 2.0 M3   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Ralf Sternberg CLA 2012-08-28 18:25:10 EDT 
When a UICallback is active and a session timeout occurs, the standing UICallBack request is released, but without the command to send another ui request. This seems to be contrary to the contract that while a UICallBack is active, the client is notified of any changes. With the current implementation, the client keeps showing the UI that was valid when the session timed out. The user is not informed of the session timeout and would assume that there are no updates, even if there are.

I propose to include the "sendUIRequest" command in the UICallBack response in case of a session timeout. The client would then send another UI request which leads to the session timeout message. As an alternative, this issue will probably be solved by the change proposed in bug 382613 comment 1.
Comment 1 Ralf Sternberg CLA 2012-10-31 08:50:17 EDT 
This issue has been fixed together with bug 382613.
In case of a session timeout, the standing request is answered and the client sends a new UI request. This request is responded with an HTTP 403 Forbidden because of the session timeout and the client displays the session timeout message.