Community
Participate
Working Groups
The outcome should allow to easily setup a scenario where 1. two or more servlet engines are configured to form a cluster 2. a simple web aplication can be deployed on the cluster nodes (given a class that implements IEntryPoint and a thereof generated web.xml should suffice to make up for a web application for the first iteration) 3. some helper classes aid in sending requests to a cluster node 4. a failover can be simulated (e.g. terminating a cluster node) 5. further requests can be sent to a different cluster node 6. the server-side state of any session on any node an be examined to allow assertions in the form display-from-session-1-in-node-A is equal to display-from-session-1-in-failover-node Ideally the above could be expressed in a JUnit test case. To ease access, all components described above would run in the same VM.
Created attachment 194671 [details] Cluster Testfixure for RWT This patch contains three projects: org.eclipse.rap.rwt.cluster.test (webapp and cluster tests) org.eclipse.rap.rwt.cluster.testfixture (cluster test support) org.eclipse.rap.rwt.cluster.testfixture.test (tests for the cluster test support :) Additional dependencies: Jetty 7 and H2 (Jetty with jdbc clustering) plus org.apache.commons.codec, org.apache.commons.logging, org.apache.commons.httpclient;bundle-version="[3.0.1,3.1.0)"
Refactored patch and applied it to CVS HEAD. Opened "CQ 5151":https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5151 to request the use of H2 from Orbit
