]
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
(
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: