Community
Participate
Working Groups
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.
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.