[
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