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

Bug 341761

Summary: Enable RWT to be used with standard servlet clustering configurations
Product: [RT] RAP Reporter: Rüdiger Herrmann <ruediger.herrmann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: beyhan.veliev
Version: 1.4   
Target Milestone: 1.5   
Hardware: All   
OS: All   
Whiteboard: plan-version=1.5 plan-theme=enterprise plan-status=committed
Bug Depends on: 351148, 353117, 353183, 260117, 309924, 341763, 342131, 342302, 342407, 342846, 344331, 344661, 345119, 348224, 348315, 350025, 350835, 351585, 358253, 359054, 359741, 361753    
Bug Blocks:    

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.