[
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