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

Bug 359741

Summary: Provide API to enable session-failover clustering in RWT
Product: [RT] RAP Reporter: Rüdiger Herrmann <ruediger.herrmann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: 1.5 M3   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 341761    

Description Rüdiger Herrmann CLA 2011-10-03 13:38:24 EDT 
To enable support for session-failover for high availability-clustering in RWT, settings in several places have to be made:
* the JEE-compatible life cycle mode has to be chosen
* an additional filter has to be registered in the web.xml
* a specialized Synchronizer has to be installed if working with background threads is desired
(see http://wiki.eclipse.org/RAP/RWT_Cluster#How_to_setup_RWT_in_a_cluster)

This should be simplified. Ideally a single method call (e.g. ApplicationConfiguration#enableSessionFailover) would be necessary to enable session-failover.
Comment 1 Rüdiger Herrmann CLA 2011-10-08 09:57:30 EDT 
An OparationMode was introduced to distinguish between STANDARD, JEE_COMPATIBLE and SESSION_FAILOVER. Via the setOparationmode method of class ApplicationConfiguration, the desired mode can be chosen. 
In STANDARD mode, which is the default, the RWTLifeCyclelife is chosen. If JEE_COMPATIBLE or SESSION_FAILOVER is selected, the threadless life cycle is activated. For SESSION_FAILOVER mode there is also the required servlet filter registered. To do that programmatically, this mode requires the servlet API 3.0.

Suggestions for another name for OperationMode are welcome.