[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-78.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.0.0
Fix is to have the contextCreated listener (in BridgeImpl) check to see if the
portlet name the bridge adds to every request matches the portlet name from the
bridges private data member holding the config object. If they match then this
bridge instance is the real target of this contextCreated and its safe to add
the portletConfig.
> Wrong PortletConfig used in EL when multiple portlets
> -----------------------------------------------------
>
> Key: PORTLETBRIDGE-78
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-78
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 1.0.0-beta, 2.0.0-alpha
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 1.0.0, 2.0.0
>
>
> The bridge adds the PortletConfig to the ELContext in a context (created)
> listener. Unfortunately this listener is registered on a per application
> basis not a per portlet basis. So when multiple portlets in the same web app
> are in the same page -- the listener is called N times -- once per bridge
> (there is a 1 bridge instance per portlet relationship). The way the code
> is written -- the first listener calls sets the PortletConfig and this is
> used in all the bridge instances EL. I.e. if you have N portlets in the same
> web app on the same page and you use EL in each to print out the portlet name
> (portletConfig.getName()) you wil see the same name in each window.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
