deleted test directory

redhat-cop · sabre1041 · Oct 14, 2016 · Sep 27, 2016 · Sep 27, 2016 · Sep 28, 2016
commit dfc8d5a529f7822faa1182bcf25d52f1e3d004c1
diff --git a/s2i-liberty/readme.md b/s2i-liberty/readme.md
@@ -21,6 +21,7 @@ This demonstration describes how to produce a new Source to Image (S2I) runtime
 		* [Binary Source](#binary-source)
 	* [Create the build config](#create-the-build-config)	
 	* [Create A New Application](#create-a-new-application)
+    * [Considerations on HTTP session failover](#considerations-on-http-session-failover)	
 
 
 ## Overview
@@ -153,6 +154,8 @@ The liberty runtime image expects:
 * any deployable artifacts in the $WORKDIR/artifacts directory
 * any [Liberty configuration files] (http://www.ibm.com/support/knowledgecenter/SSAW57_liberty/com.ibm.websphere.wlp.nd.doc/ae/cwlp_config.html) in the $WORKDIR/config directory 
 
+As you can notice the runtimeArtifacts section mentions files by name. This implies that for this process to work the artifact created by the builder image have to be always the same. I expect improvements on this front in future releases of OpenShigt but for now this is a constraint that must be kept in mind.
+
 ### Create a new Application
 
 To demonstrate the usage of the newly created builder and runtime images, a Jee example application will be built and deployed to Liberty using the Source to Image process. 
@@ -183,4 +186,11 @@ oc logs builds/<build_name>
 
 *Note: Replace `<build_name>` with the name of the build found in the previous command.*
 
-Once the build completes, the application will be deployed.
+Once the build completes, the application will be deployed.
+
+## Considerations on http session failover
+
+When liberty is deployed in a cloud environment certain limitation applies as explained in this [document](http://www.ibm.com/support/knowledgecenter/en/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/cwlp_paas_restrict.html).
+With respect to the http session failover, two techniques generally apply:
+1. session replication: Liberty does not support session replication out-of-the-box. This feature can be implemented by integrating with eXtremeScale, as described in this [article]().  
+2. session persistence: it is possible to persist the session using any database that support a JDBC connection. This [article](http://www.ibm.com/support/knowledgecenter/en/SSD28V_8.5.5/com.ibm.websphere.base.doc/ae/tprs_cnfp.html) explains how to configure Liberty to do so.
diff --git a/s2i-liberty/test/run b/s2i-liberty/test/run
diff --git a/s2i-liberty/test/test-app/README.md b/s2i-liberty/test/test-app/README.md
diff --git a/s2i-liberty/test/test-app/pom.xml b/s2i-liberty/test/test-app/pom.xml
diff --git a/s2i-liberty/test/test-app/src/main/java/.gitkeep b/s2i-liberty/test/test-app/src/main/java/.gitkeep
diff --git a/s2i-liberty/test/test-app/src/main/java/Test.java b/s2i-liberty/test/test-app/src/main/java/Test.java
diff --git a/s2i-liberty/test/test-app/src/main/java/Test2.bak b/s2i-liberty/test/test-app/src/main/java/Test2.bak
diff --git a/s2i-liberty/test/test-app/src/main/resources/.gitkeep b/s2i-liberty/test/test-app/src/main/resources/.gitkeep
diff --git a/s2i-liberty/test/test-app/src/main/webapp/images/jbosscorp_logo.png b/s2i-liberty/test/test-app/src/main/webapp/images/jbosscorp_logo.png
diff --git a/s2i-liberty/test/test-app/src/main/webapp/index.html b/s2i-liberty/test/test-app/src/main/webapp/index.html