[
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