Bug 981585 - Session key on remote WSRP portlets not unique
Summary: Session key on remote WSRP portlets not unique
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.1.1.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Thomas Heute
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 983898
TreeView+ depends on / blocked
 
Reported: 2013-07-05 08:05 UTC by Adam Kovari
Modified: 2018-12-02 16:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 983898 (view as bug list)
Environment:
EPP 5.1.1
Last Closed: 2014-09-26 07:42:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNWSRP-369 0 Major Resolved Portlet sessions are not properly scoped on consumer 2014-07-24 09:58:36 UTC

Description Adam Kovari 2013-07-05 08:05:09 UTC 
Description of problem:
We have created a remote portlet (wsrp) which saves a value as session
attribute:

  request.getPortletSession().setAttribute("inputValue", inputValue)

and retrieves it again

  String inputValue = (String)
  request.getPortletSession().getAttribute("inputValue");

The problem is, that if we are placing the portlet twice one the same
page, both portlets are showing the same inputValue. So the
setAttribute() and getAttribute() method is not unique for the portlet
instance.

Version-Release number of selected component (if applicable):
EPP 5.1.1

How reproducible:
Always

Steps to Reproduce:
1. See description

Actual results:
Portlet Session attributes shared accross same portlets on one page

Expected results:
Portlet Session attributes not shared accross same portlets on one page

Additional info:
Note You need to log in before you can comment on or make changes to this bug.