[JBoss JIRA] Created: (GTNWCI-15) Portlets and servlets within the same .war don't share the same session
4:22 p.m.
Portlets and servlets within the same .war don't share the same session
-----------------------------------------------------------------------
Key: GTNWCI-15
URL: https://jira.jboss.org/jira/browse/GTNWCI-15
Project: GateIn Web Container Integration
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: GateIn with JBoss - 3.0-Final, GateIn with Tomcat - 3.0-Final
Reporter: Marko Strukelj
Servlets don't see an already existing session previously used by portlets in the same
.war, as required by Portlet Spec.
The consequence of this is that if you use
PortletSession.setAttribute("someAttr", "Some value",
PortletSession.APPLICATION_SCOPE) in your portlet and
HttpSession.getAttribute("someAttrs") in your servlet, the servlet will get
null, because it uses a session with a different id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:58 p.m.
New subject: [JBoss JIRA] Updated: (GTNWCI-15) Portlets and servlets within the same .war don't share the same session
[
https://jira.jboss.org/jira/browse/GTNWCI-15?page=com.atlassian.jira.plug...
]
Marko Strukelj updated GTNWCI-15:
---------------------------------
Attachment: portlet_with_servlet.zip
Attached portlet_with_servlet.zip.
I can compile this against latest portal trunk - I extract portlet_with_servlet.zip into
portal/trunk/examples/portlets,
'cd portlet_with_servlet' and 'mvn install'.
Deploy as usually. The portlet is called 'ExampleFillSessionPortlet'.
When deployed the portlet displays a form. It takes a number, sets it via portlet and
displays it via servlet in the next line. Session state is logged to console so you can
see two sessions being created.
Portlets and servlets within the same .war don't share the same
session
-----------------------------------------------------------------------
Key: GTNWCI-15
URL: https://jira.jboss.org/jira/browse/GTNWCI-15
Project: GateIn Web Container Integration
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: GateIn with JBoss - 3.0-Final, GateIn with Tomcat - 3.0-Final
Reporter: Marko Strukelj
Attachments: portlet_with_servlet.zip
Servlets don't see an already existing session previously used by portlets in the
same .war, as required by Portlet Spec.
The consequence of this is that if you use
PortletSession.setAttribute("someAttr", "Some value",
PortletSession.APPLICATION_SCOPE) in your portlet and
HttpSession.getAttribute("someAttrs") in your servlet, the servlet will get
null, because it uses a session with a different id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 p.m.
New subject: [JBoss JIRA] Commented: (GTNWCI-15) Portlets and servlets within the same .war don't share the same session
[
https://jira.jboss.org/jira/browse/GTNWCI-15?page=com.atlassian.jira.plug...
]
Matt Wringe commented on GTNWCI-15:
-----------------------------------
A few comments on this, this is probably not a wci issue. Test for this are usually done
through the portlet container, and they all pass on tomcat and jboss.
For the pc jboss tests we needed to make a one line change to the context.xml, and this
should have been added to the gatein setup (I believe I already added this at point point
in the beginning of the integration between JBoss Portal and eXo Portal, but I guess this
must have gotten lost at some point). For issue in jboss its an easy fix, we just need to
make a simple configuration change.
The issue in tomcat is a bit more confusing, I need to look into it a bit more. For the pc
tests we don't need to make any changes, so it must be something we are changing with
the GateIn setup which is causing the problems.
There is a problem with the example's javascript when used in firefox, console is not
defined. I can only run the example using chrome
Portlets and servlets within the same .war don't share the same
session
-----------------------------------------------------------------------
Key: GTNWCI-15
URL: https://jira.jboss.org/jira/browse/GTNWCI-15
Project: GateIn Web Container Integration
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: GateIn with JBoss - 3.0-Final, GateIn with Tomcat - 3.0-Final
Reporter: Marko Strukelj
Attachments: portlet_with_servlet.zip
Servlets don't see an already existing session previously used by portlets in the
same .war, as required by Portlet Spec.
The consequence of this is that if you use
PortletSession.setAttribute("someAttr", "Some value",
PortletSession.APPLICATION_SCOPE) in your portlet and
HttpSession.getAttribute("someAttrs") in your servlet, the servlet will get
null, because it uses a session with a different id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:51 p.m.
New subject: [JBoss JIRA] Commented: (GTNWCI-15) Portlets and servlets within the same .war don't share the same session
[
https://jira.jboss.org/jira/browse/GTNWCI-15?page=com.atlassian.jira.plug...
]
Marko Strukelj commented on GTNWCI-15:
--------------------------------------
My bad regarding javascript issues in attached example.
In functions.js all occurences of 'console &&' should be replaced by
'window.console &&'.
Matt: Can you share the solution to the problem on JBoss?
Portlets and servlets within the same .war don't share the same
session
-----------------------------------------------------------------------
Key: GTNWCI-15
URL: https://jira.jboss.org/jira/browse/GTNWCI-15
Project: GateIn Web Container Integration
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: GateIn with JBoss - 3.0-Final, GateIn with Tomcat - 3.0-Final
Reporter: Marko Strukelj
Attachments: portlet_with_servlet.zip
Servlets don't see an already existing session previously used by portlets in the
same .war, as required by Portlet Spec.
The consequence of this is that if you use
PortletSession.setAttribute("someAttr", "Some value",
PortletSession.APPLICATION_SCOPE) in your portlet and
HttpSession.getAttribute("someAttrs") in your servlet, the servlet will get
null, because it uses a session with a different id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:07 p.m.
New subject: [JBoss JIRA] Commented: (GTNWCI-15) Portlets and servlets within the same .war don't share the same session
[
https://jira.jboss.org/jira/browse/GTNWCI-15?page=com.atlassian.jira.plug...
]
Matt Wringe commented on GTNWCI-15:
-----------------------------------
Its a simple one line change to the deploy/jbossweb.sar/context.xml file
you need to add this to the file:
<!-- Needed for portal session paths -->
<SessionCookie path="/"/>
This was a change between JBoss 4.x and JBoss 5.x that requires this to be added.
For Tomcat, we don't make any changes to the server configuration files for the pc
tests, so it has to be something in the gatein configuration that needs to change
changed.
Portlets and servlets within the same .war don't share the same
session
-----------------------------------------------------------------------
Key: GTNWCI-15
URL: https://jira.jboss.org/jira/browse/GTNWCI-15
Project: GateIn Web Container Integration
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: GateIn with JBoss - 3.0-Final, GateIn with Tomcat - 3.0-Final
Reporter: Marko Strukelj
Attachments: portlet_with_servlet.zip
Servlets don't see an already existing session previously used by portlets in the
same .war, as required by Portlet Spec.
The consequence of this is that if you use
PortletSession.setAttribute("someAttr", "Some value",
PortletSession.APPLICATION_SCOPE) in your portlet and
HttpSession.getAttribute("someAttrs") in your servlet, the servlet will get
null, because it uses a session with a different id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:06 p.m.
New subject: [JBoss JIRA] Commented: (GTNWCI-15) Portlets and servlets within the same .war don't share the same session
[
https://jira.jboss.org/jira/browse/GTNWCI-15?page=com.atlassian.jira.plug...
]
Matt Wringe commented on GTNWCI-15:
-----------------------------------
A workaround on tomcat is to specify the emptySessionPath="true" for the http
connector, but I don't know why we need to do this.
The cross context test in the pc testsuite passes fine with tomcat without such
modifications
(http://anonsvn.jboss.org/repos/gatein/components/pc/trunk/test/src/test/j...).
Portlets and servlets within the same .war don't share the same
session
-----------------------------------------------------------------------
Key: GTNWCI-15
URL: https://jira.jboss.org/jira/browse/GTNWCI-15
Project: GateIn Web Container Integration
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: GateIn with JBoss - 3.0-Final, GateIn with Tomcat - 3.0-Final
Reporter: Marko Strukelj
Attachments: portlet_with_servlet.zip
Servlets don't see an already existing session previously used by portlets in the
same .war, as required by Portlet Spec.
The consequence of this is that if you use
PortletSession.setAttribute("someAttr", "Some value",
PortletSession.APPLICATION_SCOPE) in your portlet and
HttpSession.getAttribute("someAttrs") in your servlet, the servlet will get
null, because it uses a session with a different id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:32 p.m.
New subject: [JBoss JIRA] Closed: (GTNWCI-15) Portlets and servlets within the same .war don't share the same session
[
https://jira.jboss.org/jira/browse/GTNWCI-15?page=com.atlassian.jira.plug...
]
Matt Wringe closed GTNWCI-15.
-----------------------------
Resolution: Duplicate Issue
Opened jira GTNPORTAL-1118 for the cross context sessions issues, this has now been
fixed.
Portlets and servlets within the same .war don't share the same
session
-----------------------------------------------------------------------
Key: GTNWCI-15
URL: https://jira.jboss.org/jira/browse/GTNWCI-15
Project: GateIn Web Container Integration
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: GateIn with JBoss - 3.0-Final, GateIn with Tomcat - 3.0-Final
Reporter: Marko Strukelj
Attachments: portlet_with_servlet.zip
Servlets don't see an already existing session previously used by portlets in the
same .war, as required by Portlet Spec.
The consequence of this is that if you use
PortletSession.setAttribute("someAttr", "Some value",
PortletSession.APPLICATION_SCOPE) in your portlet and
HttpSession.getAttribute("someAttrs") in your servlet, the servlet will get
null, because it uses a session with a different id.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5180
days inactive
5187
days old
6 comments
2 participants
participants (2)
-
Marko Strukelj (JIRA) -
Matt Wringe (JIRA)