++ This bug is a clone of bug 793724 ++
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?
Release Notes Docs Status: Added: Not Required
Primary SME: Added: theute
Labels: Added: EPP_6_0_0_Candidate
*** Bug 793724 has been marked as a duplicate of this bug. ***
This one needs to be investigated - not sure if events are duable in current situation however we should consider supporting passing public render parameters
According specification about Events:
PLT.15.2.5 Event Processing:
"Events are valid only in the current client request and the portlet container must therefore deliver all events within the current client request. [...]"
So, a modification to share Events between pages should force to break specification if we try to apply a change inside PortletContainer.
A valid workaround for this use case can be to use EventFilter interface and share Events through PortletSession object as several requests are needed.
The use case described in the BZ (applications migrated from IBM/Oracle to JPP) can be achieved adding a helper Filter that shares Events across requests.
About Public Render Parameters:
Public Render Parameters are saved at container level, so by default there are shared between requests in the current version, so public render parameters can be shared between pages by default.
Fixed in GateIn master (3.7.x).
We are evaluating if we can also add Public Render Parameters support at URL level.
I change to ASSIGN status to report progress in this BZ.
Sent patch to support public render parameters from URL with propagation between pages.
The patch named in Comment #10 was merged in upstream.