You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Matt Bishop (JIRA)" <ji...@apache.org> on 2007/01/24 22:16:49 UTC
[jira] Created: (PLUTO-289) Two portlet windows of the same portlet
are sharing their PORTLET_SCOPE attributes
Two portlet windows of the same portlet are sharing their PORTLET_SCOPE attributes
----------------------------------------------------------------------------------
Key: PLUTO-289
URL: https://issues.apache.org/jira/browse/PLUTO-289
Project: Pluto
Issue Type: Bug
Components: portlet container
Affects Versions: 1.1.0-beta2
Environment: Mac OS X 10.4.8, JDK 1.5.0_06
Reporter: Matt Bishop
If I create two instance windows of the same exact portlet like this (in pluto-portal-driver-config.xml):
<page name="Test Page" uri="/WEB-INF/themes/pluto-default-theme.jsp">
<portlet context="/testsuite" name="TestPortlet1"/>
<portlet context="/testsuite" name="TestPortlet2"/>
<portlet context="/testsuite" name="TestPortlet2"/>
</page>
Both windows for TestPortlet2 react to user events and do not keep separate state as expected. I think this is because the Windows are sharing IDs rather than creating unique IDs for each window instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-289) Two portlet windows of the same
portlet are sharing their PORTLET_SCOPE attributes
Posted by "Matt Bishop (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467155 ]
Matt Bishop commented on PLUTO-289:
-----------------------------------
This bug does not exist in Pluto 1.0.1; each TestPortlet2 instance reacts individually to user events.
> Two portlet windows of the same portlet are sharing their PORTLET_SCOPE attributes
> ----------------------------------------------------------------------------------
>
> Key: PLUTO-289
> URL: https://issues.apache.org/jira/browse/PLUTO-289
> Project: Pluto
> Issue Type: Bug
> Components: portlet container
> Affects Versions: 1.1.0-beta2
> Environment: Mac OS X 10.4.8, JDK 1.5.0_06
> Reporter: Matt Bishop
>
> If I create two instance windows of the same exact portlet like this (in pluto-portal-driver-config.xml):
> <page name="Test Page" uri="/WEB-INF/themes/pluto-default-theme.jsp">
> <portlet context="/testsuite" name="TestPortlet1"/>
> <portlet context="/testsuite" name="TestPortlet2"/>
> <portlet context="/testsuite" name="TestPortlet2"/>
> </page>
> Both windows for TestPortlet2 react to user events and do not keep separate state as expected. I think this is because the Windows are sharing IDs rather than creating unique IDs for each window instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PLUTO-289) Two portlet windows of the same
portlet are sharing their PORTLET_SCOPE attributes
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David DeWolf resolved PLUTO-289.
--------------------------------
Resolution: Duplicate
> Two portlet windows of the same portlet are sharing their PORTLET_SCOPE attributes
> ----------------------------------------------------------------------------------
>
> Key: PLUTO-289
> URL: https://issues.apache.org/jira/browse/PLUTO-289
> Project: Pluto
> Issue Type: Bug
> Components: portlet container
> Affects Versions: 1.1.0-beta2
> Environment: Mac OS X 10.4.8, JDK 1.5.0_06
> Reporter: Matt Bishop
>
> If I create two instance windows of the same exact portlet like this (in pluto-portal-driver-config.xml):
> <page name="Test Page" uri="/WEB-INF/themes/pluto-default-theme.jsp">
> <portlet context="/testsuite" name="TestPortlet1"/>
> <portlet context="/testsuite" name="TestPortlet2"/>
> <portlet context="/testsuite" name="TestPortlet2"/>
> </page>
> Both windows for TestPortlet2 react to user events and do not keep separate state as expected. I think this is because the Windows are sharing IDs rather than creating unique IDs for each window instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.