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