Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342971 - Consider moving the RWTLifeCycle to session scope
Summary: Consider moving the RWTLifeCycle to session scope
Status: NEW
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-15 09:46 EDT by Rüdiger Herrmann CLA
Modified: 2011-09-15 06:31 EDT (History)
0 users

See Also:

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 Rüdiger Herrmann CLA 2011-04-15 09:46:18 EDT 
The RWTLifeCycle (and the under way being threadless life cycle, bug 341763) have application scope. This leads to code that is hard to read as all state is read and written to the session or request by using attributes. If the life cycle had session scope, its state could be held in fields which would lead to better readable code.
To maintain backward compatibility, the phase listener will probably have to remain in application scope.
What do you think?