[
https://issues.apache.org/jira/browse/PLUTO-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved PLUTO-522.
-----------------------------
Resolution: Fixed
I just wrote a quick and dirty set of pingpong portlets testing this issue
using multiple portlet apps but cannot reproduce anymore.
Assuming this was an actual bug before, I'm now resolving it as fixed.
> pluto looks up wrong context when publish an event in response to an event
> --------------------------------------------------------------------------
>
> Key: PLUTO-522
> URL: https://issues.apache.org/jira/browse/PLUTO-522
> Project: Pluto
> Issue Type: Bug
> Components: portal driver
> Reporter: Antony Stubbs
> Fix For: 2.0.0
>
>
> I am experiencing a problem where I have two portals specified in the same
> war file.
> When portal b correctly receives an event from portal a, and then in response
> also tries to publish an event (setEvent), the pluto driver, when running
> EventProviderImpl#isDeclaredAsPublishingEvent while looking up the registered
> publish event names, looks up the portlet context of portlet a (instead of b,
> as b is the portlet publishing the event), and so does not find the matching
> publish name for the event.
> The example project can be found shortly on WICKET-1620.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
