ICEfaces
  1. ICEfaces
  2. ICE-2104

ICEfaces incompatibility with Liferay when portal is deployed in a context other than ROOT

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: 1.6
          • Fix Version/s: 1.7DR#3, 1.7
          • Component/s: None
          • Labels:
            None
          • Environment:
            Tomcat 5.5.23 / Liferay 4.3.2
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            When deploying ICEfaces portlets to a Tomcat/Liferay where Liferay is deployed to a servlet context other than ROOT, ensure the emptySessionPath attribute of the Connector node is set to 'true' in Tomcat's server.xml as follows:

                <Connector port="8080" protocol="HTTP/1.1"
                           connectionTimeout="20000"
                           redirectPort="8443" URIEncoding="UTF-8"
                           emptySessionPath="true" />
            Show
            When deploying ICEfaces portlets to a Tomcat/Liferay where Liferay is deployed to a servlet context other than ROOT, ensure the emptySessionPath attribute of the Connector node is set to 'true' in Tomcat's server.xml as follows:     <Connector port="8080" protocol="HTTP/1.1"                connectionTimeout="20000"                redirectPort="8443" URIEncoding="UTF-8"                emptySessionPath="true" />

            Description

            Liferay has a customer that has a requirement to deploy Liferay in a Tomcat servlet context other than root. So as part of the training for this customer, I wrote this wiki article:

            http://wiki.liferay.com/index.php/Liferay_FAQ#How_do_I_deploy_Liferay_to_a_context_different_than_ROOT_.28starting_with_Tomcat_5.5_standalone.29

            During the training, we discovered that Liferay's sample-icefaces-sun-portlet did not work when the portal was deployed in a context named "liferay-portal". When I tried it with the portal in the ROOT context however, it worked fine.

            The modal "User Session Expired" window pops up all the time. The porlet is completely unusable.

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Neil Griffin
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: