[
http://jira.jboss.com/jira/browse/JBPORTAL-1220?page=comments#action_1235... ]
Julien Viet commented on JBPORTAL-1220:
---------------------------------------
I don't think that the checkSession() I put is necessary, it brings two things (one
good and one bad)
1/ it forces to create sessions even if not needed (bad)
2/ it forces consumers to be able to maintain session in order to use a portlet, so the
portlet will have a garantee that session support is reliable
Imho it should be a configuration option like :
<require-consumer-session-support>true</require-consumer-session-support>
which would do it or not.
WSRP session maintenance issue
------------------------------
Key: JBPORTAL-1220
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1220
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.6.Alpha1, 2.4.1 SP1
Environment: BEA Weblogic 8 as a consumer
JBoss Portal as a producer
Reporter: Julien Viet
Assigned To: Chris Laprun
Fix For: 2.6.CR1, 2.4.2 Final
Attachments: Session.patch
When the portal creates a session (done by the portlet container) the cookie is sent to
the consumer but it does not send the cookie back.
The solution I found that works (tested by a user from our community) is to leverare
initCookie() to create an HTTP Session.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira