ICEfaces
  1. ICEfaces
  2. ICE-3498

User Session Expired - OC4J and Liferay 4.4.1 not deployed under Root context

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 1.7
    • Fix Version/s: None
    • Component/s: Bridge, ICE-Components
    • Labels:
      None
    • Environment:
      OC4J 10.1.3.4
      Liferay 4.4.1
      Icefaces 1.7.1
      Windows XP

      Description

      Common user session expired message pops up upon addition of icefaces portlet to liferay on oc4j. I have found workarounds for Tomcat such as setting emptySessionPath=true. Are there any workarounds for OC4j. I have also found the updated web.xml for OC4J due to the requestdispatcher problem, where I setup the Main Servlet with the mappings as shown in the sample web.xml. This problem has stopped prouction of icefaces portlets for us and we may have to take a look at other technologies if we cannot find a workaround.

      The emptysessionpath=true tracker http://jira.icefaces.org/browse/ICE-2104

      thanks for any help that you can provide.

        Issue Links

          Activity

          Hide
          Aaron Lucas added a comment -

          I have also tried deploying Liferay as root ("/") with no luck.

          Show
          Aaron Lucas added a comment - I have also tried deploying Liferay as root ("/") with no luck.
          Hide
          Aaron Lucas added a comment -

          See here
          http://forum.springframework.org/archive/index.php/t-41990.html

          Setting private-session-attributes to false fixes most portlet but I have experience using Tomcat 6 and Liferay using icefaces where setting this attribute stomps on icefaces, according to deryk sinotte see here:
          http://www.icefaces.org/JForum/posts/list/30/9386.page

          This problem needs to be addressed as far as the interoperability with Liferay and their properties. To find out more about this property see here

          http://longgoldenears.blogspot.com/2008/03/liferay-session-sharing-demystified.html

          Show
          Aaron Lucas added a comment - See here http://forum.springframework.org/archive/index.php/t-41990.html Setting private-session-attributes to false fixes most portlet but I have experience using Tomcat 6 and Liferay using icefaces where setting this attribute stomps on icefaces, according to deryk sinotte see here: http://www.icefaces.org/JForum/posts/list/30/9386.page This problem needs to be addressed as far as the interoperability with Liferay and their properties. To find out more about this property see here http://longgoldenears.blogspot.com/2008/03/liferay-session-sharing-demystified.html
          Hide
          Aaron Lucas added a comment -

          A sample app that I was talking about using the liferay parameter

          Show
          Aaron Lucas added a comment - A sample app that I was talking about using the liferay parameter
          Hide
          Ken Fyten added a comment -

          Marking as Closed / Invalid as part of legacy ICEfaces ICE / Compat component JIRA cleanup.

          Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf

          If the issue persists with the current ICEfaces release, please create a new JIRA for it.

          Show
          Ken Fyten added a comment - Marking as Closed / Invalid as part of legacy ICEfaces ICE / Compat component JIRA cleanup. Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf If the issue persists with the current ICEfaces release, please create a new JIRA for it.

            People

            • Assignee:
              Unassigned
              Reporter:
              Aaron Lucas
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: