JBossDeveloper

Still dorothy you didn't provide us your usecase, why do you need this feature ? (Any concrete example as helmer provided ?)

Ok, so for this you don't need what has been discussed here (cross page eventing).
In fact the scenario you mentioned is a scenario that is used in the samples that you can deploy on JBoss Portal. There is a menu on the left column to open various pages on which there are various samples.

Also I am surprised (or I misunderstood) that what you describe works with portal events in other portals, the portal shouldn't redirect you on event listening.

You can achieve the same thing with JBoss Portal check the samples.

As you mention the only spec that exists in that domain is the JSR-286 spec which doesn't concern the notion of pages. The thing you mention is proprietary to WPS, so of course it will work with WPS and of course won't work the same way in JBoss Portal. I hope you understand this.

Now the notion of events are made to trigger events in a blind way, one portlet should be able to emit events without caring who's listening, same for listeners they shouldn't have to care if there are other listeners.

If the event redirect from page to page, that can lead to interesting things, the page you will land is then totally random.

So now the question is 'do we call the event phase from portlets that are not on the same page from the current one ?', so far I haven't seen a usecase where this should happen, and this is not helping our users/customers to allow this as most scenarios I heard of are mis-understanding of what the events in JSR-286 are about (UI).

Now, hilmer's idea requires to not only trigger the event phase from other pages but also the render phase and 'somehow' dynamically update the content on the opened page which should start with a proof of concept if there is any picker on this idea :)

I don't see how the scenario you mention relates to that, from what i read you just want to build URLs to call other pages in fact in that case you would not even want portlets from the same page to listen to the event.

This is part of the extension to the PortletRequest that we provide, see the catalog portlet: https://svn.jboss.org/repos/portal/tags/JBoss_Portal_2_7_2/core-samples/src/main/org/jboss/portal/core/samples/catalog/CatalogPortlet.java

Yes, exactly.
Events mechanism need to be deterministic. And a portlet emitting an event should not worry about the various event wirings.

If we take your example further, Page A, Page B, page C with respective Portlet A, Portlet B, Portlet C

say an event submitted from a link on Portlet A is wired to Portlet B and Portlet C, on which page will you land ? (ordering of wires in not an option ;) )

If you are looking for a solution that would work accross all portals, you won't be able to achieve that, you can create cross-portal-vendor *portlets* but not cross-portal-vendor *portals* (unless you defined a complex level of abstraction between vendors)

Sorry for the link:
http://anonsvn.jboss.org/repos/portal/tags/JBoss_Portal_2_7_2/core-samples/src/main/org/jboss/portal/core/samples/catalog/CatalogPortlet.java

For Jira, the url is http://jira.jboss.org, there is a JBoss Portal project where anyone can open a feature request. But to be implemented we would first need to agree on the feature, because this won't solve *your* usecase.

"Create new issue" at the top of the screen.

If you create a JIRA issue for this, please reference this forum post in the appropriate field of the JIRA issue as well.