Bug 793725 - Re-evalute the functionality that allows Portlet Event and Public Render Parameter to be propagated to portlets on different pages.
Summary: Re-evalute the functionality that allows Portlet Event and Public Render Para...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise Portal Platform 4
Classification: JBoss
Component: Portal
Version: 4.3.0.GA_CP6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard: EPP_6_0_0_Candidate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-09 21:24 UTC by Gary Hu
Modified: 2025-02-10 03:15 UTC (History)
0 users

Fixed In Version:
Clone Of: JBEPP-797
Environment:
Last Closed: 2025-02-10 03:15:12 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-797 0 Major Closed Re-evalute the functionality that allows Portlet Event and Public Render Parameter to be propagated to portlets on diffe... 2013-03-05 16:14:26 UTC

Description Gary Hu 2011-02-09 21:24:54 UTC 
++ This bug is a clone of bug 793724 ++

project_key: JBEPP

The current implementation of EPP 4.3 and 5.x doesn't enable the Portlet Event to be propagated to portlets that are on different pages. The Public Render Parameter seems to be work that way possibly because of some unexpected side effects. 

We've seen some needs from the customers, especially coming from IBM/Oracle portals where the similar functionality is available. Can we re-evaluate this functionality to see if we can make it available in our future release?
Comment 2 Jared MORGAN 2011-11-16 23:52:22 UTC 
Release Notes Docs Status: Added: Not Required
Primary SME: Added: theute
Comment 3 hfnukal@redhat.com 2012-01-16 12:47:50 UTC 
Labels: Added: EPP_6_0_0_Candidate
Comment 5 Red Hat Bugzilla 2025-02-10 03:15:12 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.