Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341761 - Enable RWT to be used with standard servlet clustering configurations
Summary: Enable RWT to be used with standard servlet clustering configurations
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: plan-version=1.5 plan-theme=enterpris...
Keywords:
Depends on: 351148 353117 353183 260117 309924 341763 342131 342302 342407 342846 344331 344661 345119 348224 348315 350025 350835 351585 358253 359054 359741 361753
Blocks:
  Show dependency tree
 
Reported: 2011-04-04 06:39 EDT by Rüdiger Herrmann CLA
Modified: 2012-04-24 17:39 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-04-04 06:39:52 EDT
Currently, RWT cannot be used in scenarios where transparent session failover is required. Section 7.7.2 (Distributed Environments) of the servlet 2.3 specification desribes what the minimum requirements are.
The two main obstacles that prevent RWT to be used in such scenarios are:
* RWT creates a UI thread for each session to be comtaible with SWT. This thread prevents sessions from being migrated among servlet container nodes
* the servlet spec requires all session attributes to be serializable if the session is to be distributed. None of the session attributes maintained by RWT are serializable.

This bug is to serve mostly as a meta-bug to capture the problem and track the solution.
Comment 1 Ralf Sternberg CLA 2012-04-24 17:39:43 EDT
With version 1.5, RWT supports transparent session failover in servlet clustering configurations. Therefore I consider this planning item as solved even though a few open issues remain. The remaining issues are tracked by separate bugs.