Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 387360 - RAP: When leaving the Rap application and going back a new session is started
Summary: RAP: When leaving the Rap application and going back a new session is started
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-16 05:36 EDT by Stephan Leicht Vogt CLA
Modified: 2021-08-19 11:11 EDT (History)
2 users (show)

See Also:
claudio.guglielmo: juno+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Leicht Vogt CLA 2012-08-16 05:36:06 EDT 
When leaving the Rap application and going back a new session is started. This should not happen.
If going backwards in the browser history from a Internet url back to the scout application the old session should be reused - if it is still available on the webappserver.
Comment 1 Claudio Guglielmo CLA 2012-12-13 10:49:48 EST 
The problem can be solved in the following way:
The ClientSession should be bound to the http session, and not to the rap session as it is now. With that, the ClientSession can be reused on a page reload. This gives following advantages:
- The state can be restored: Every element on the scout desktop (views, dialogs, messageboxes) along with their states can be showed again after a page reload. 
- The reload is faster because the ClientSession doesn't need to be loaded again.

This would also change the shutdown behaviour in the following way: The rap session along with the Display and RwtEnvironment get destroyed, but the scout model not. Therefore it's important that the gui properly detaches from the model, so that the memory is cleaned up properly.
The ClientSession gets destroyed on http session invalidation, which happens on session timeout or logout.
Comment 2 Claudio Guglielmo CLA 2012-12-13 11:10:40 EST 
Implemented for 3.8.2.

Hint: After a page reload, the browser back and forward buttons won't work as expected. They work only for navigation points which are visited AFTER the reload. The reason is described in the following rap ticket: Bug 396400.
Comment 3 Matthias Zimmermann CLA 2013-03-04 06:11:34 EST 
Bug closed, shipped with 3.8.2 (Juno, SR2)