You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Peter Meier (JIRA)" <je...@jakarta.apache.org> on 2005/02/10 21:56:13 UTC
[jira] Created: (JS2-208) Inter-portlet Communication
Inter-portlet Communication
---------------------------
Key: JS2-208
URL: http://issues.apache.org/jira/browse/JS2-208
Project: Jetspeed 2
Type: New Feature
Components: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
Versions: 2.0-M1
Reporter: Peter Meier
Attachments: jetspeed-2-diff.zip, portlet-event.zip
As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "garpinc (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_64226 ]
garpinc commented on JS2-208:
-----------------------------
Shouldn't you submit it for latest head version?
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Container, Other, Struts Portlet, Components Core, Assembly/Configuration
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "Sven Thiergen (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_65859 ]
Sven Thiergen commented on JS2-208:
-----------------------------------
I took Peter's example and integrated it against the current CVS HEAD. It was possible almost without changes, except that the "Fragment" type in "NotificationValveImpl" and "PortletStackValveImpl" needed to changed to "ContentFragment". This traces down to "request.getPage().getRootFragment()" which I changed to "...getRootContentFragment()". Hope this is no problem; I am unaware of real meaning of the methods.
My first example did not work, but it was the first try so maybe I am doing something wrong. I can put in another day or two to get the thing working.
Regarding design:
The changes in the Pluto classes probably really need to change. They introduce a dependency to Jetspeed2 (usage of class "BasePortletEvent") which certainly isn't possible. Fortunately, only a static method is used which swaps around a parameter from a Map into a HttpServletRequest.
Ate suggested to synthesize an ActionRequest; instead of doing a real Redirect. Seems like the best solution regarding performance and cleanliness; so the Pluto code has not to be touched at all. Can someone give me some hints how to do this?
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-208) Inter-portlet Communication
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=all ]
Ate Douma updated JS2-208:
--------------------------
Fix Version/s: (was: 2.1)
Resolution will take too much time to make it for the 2.1 release
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: Assembly/Configuration, Components Core, Other, Struts Portlet, Container
> Affects Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "Ate Douma (JIRA)" <je...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_59138 ]
Ate Douma commented on JS2-208:
-------------------------------
Peter, I think you forgot to attach the demos... ;-)
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[jira] Updated: (JS2-208) Inter-portlet Communication
Posted by "Peter Meier (JIRA)" <je...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=history ]
Peter Meier updated JS2-208:
----------------------------
Attachment: jetspeed-2-diff.zip
portlet-event.zip
Attached are two zip files, which contain (a) the portlet event notification package, and (b) the changes that need to be applied to Jetspeed-2. All changes are highlighted and commented.
Please read docs/description.html in jetspeed-2-diff to begin with.
I appreciate any comments or feedback.
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "garpinc (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_64235 ]
garpinc commented on JS2-208:
-----------------------------
Perhaps then maybe instead you should check out by date. That will be stable if you pick a date prior to today. That way the integration effort required by the committer team will not be great and it will be far more likely they will integrate it before M3.
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Container, Other, Struts Portlet, Components Core, Assembly/Configuration
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "Peter Meier (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_64221 ]
Peter Meier commented on JS2-208:
---------------------------------
I have an updated version for Jetspeed-2 M2 available, I will submit it in a couple of days or so.
Peter.
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Container, Other, Struts Portlet, Components Core, Assembly/Configuration
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Updated: (JS2-208) Inter-portlet Communication
Posted by "Peter Meier (JIRA)" <je...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=history ]
Peter Meier updated JS2-208:
----------------------------
Attachment: portlet-events-demos.zip
Here is the promised demo. I've had to overcome some issues with our firewall to let me upload things.
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "Peter Meier (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_64232 ]
Peter Meier commented on JS2-208:
---------------------------------
Please keep in mind that inter-portlet communication is not part of the official Jetspeed-2 code base (yet ;-). As a non-committer, I need a stable reference point I can develop against. The latest head version is a moving target. Every time a committer checks in code, it might break the IPC solution.
Peter
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Container, Other, Struts Portlet, Components Core, Assembly/Configuration
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [jira] Updated: (JS2-208) Inter-portlet Communication
Posted by Jonathan Hawkins <jo...@hawkinsweb.co.uk>.
Can you give me details of this.
Thanks
Jon Hawkins
Michael Lipp (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/JS2-208?page=all ]
>
>Michael Lipp updated JS2-208:
>-----------------------------
>
> Fix Version: 2.0-POST
> Description:
>As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
>The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
>
> was:
>As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
>The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
>
> Environment:
>
>
>
>>Inter-portlet Communication
>>---------------------------
>>
>> Key: JS2-208
>> URL: http://issues.apache.org/jira/browse/JS2-208
>> Project: Jetspeed 2
>> Type: New Feature
>> Components: Assembly/Configuration, Components Core, Other, Struts Portlet, Container
>> Versions: 2.0-M1
>> Reporter: Peter Meier
>> Fix For: 2.0-POST
>> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>>
>>As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
>>The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
>>
>>
>
>
>
[jira] Updated: (JS2-208) Inter-portlet Communication
Posted by "Michael Lipp (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=all ]
Michael Lipp updated JS2-208:
-----------------------------
Fix Version: 2.0-POST
Description:
As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
was:
As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
Environment:
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Other, Struts Portlet, Container
> Versions: 2.0-M1
> Reporter: Peter Meier
> Fix For: 2.0-POST
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "Peter Meier (JIRA)" <je...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_59135 ]
Peter Meier commented on JS2-208:
---------------------------------
Attached are two simple inter-portlet communications demos, one using JSR 168 portlets, the other using Struts portlets. They are intended to highlight the principles of portlet event notifications and to show how to use the Portlet Event API.
Contained are four portlets, which are arranged in three portal pages in a mix and match fashion.
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "Ate Douma (JIRA)" <je...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_59049 ]
Ate Douma commented on JS2-208:
-------------------------------
Peter, I finally found a short time today for a first look at your code and documentation.
I must say, I'm impressed by the completeness and scope.
But, I haven't had time for testing so this is yet only based on a short code review ;-)
I do have already a few questions for you:
- Are you planning/able to update the code to the J2 cvs-head codebase?
As it is currently based on the J2 2.0M1 codebase I would need to go back to that
before I would be able to test it, and although possible its not something I prefer.
- Do you have any showcase portlets (code) available?
It would help (me) a lot to have a working example to play with.
- I noticed you had to modify the Pluto PortletContainer(Impl) to trap its redirecting.
Have you considered providing a wrapped request to Pluto which might be able to do the
same (I'm not sure, just asking). I don't like the idea to have to hack Pluto if its isn't
absolutely necessary.
- I like the general idea of translating a PortletEvent to an (additional) ActionRequest for
a targeted Portlet as for that Portlet it is as if it is invoked by the user directly.
What I'm not sure about yet is how you handle ActionResponse.setRenderParameter() calls done
by the thus invoked Portlet: will new renderParameters be set on the eventually produced
RenderURL?
It looks like the initial RenderURL produced after the ActionRequest from the Portlet
firing the first PortletEvent prevails but I'm not sure.
I think that if a new ActionRequest is invoked as result of a PortletEvent the formal behavior
of the Portlet API must be maintained, including effective setRenderParameter calls.
- You implemented the invocation of a new ActionRequest using real redirects. Might it be
possible to just synthesize a new ActionRequest without the need for a client side redirect?
It might make state handling much easier and lighter: maybe use ThreadLocals instead of storing
state in a HashMap keyed on SessionId as you do now.
Also, by intercepting the (initial) ActionRequest, you then also wouldn't need to hack the Pluto
PortletContainer but first process all the PortletEvents before letting Pluto perform the final
redirect.
I'll try to find some more time this weekend to delve deeper into your code.
Ate
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "Michael Lipp (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_12355958 ]
Michael Lipp commented on JS2-208:
----------------------------------
Jonathan Hawkins (jonathan.hawkins@hawkinsweb.co.uk) just sent me a pointer to http://www.doc.ic.ac.uk/~mo197/portlets/portlet_messaging/index.php. Maybe this library should be considered when the issue is revisited (just saving information).
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Assembly/Configuration, Components Core, Other, Struts Portlet, Container
> Versions: 2.0-M1
> Reporter: Peter Meier
> Fix For: 2.0-POST
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-208) Inter-portlet Communication
Posted by "garpinc (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-208?page=comments#action_64173 ]
garpinc commented on JS2-208:
-----------------------------
What's the latest with this. Will it make it for M3?
> Inter-portlet Communication
> ---------------------------
>
> Key: JS2-208
> URL: http://issues.apache.org/jira/browse/JS2-208
> Project: Jetspeed 2
> Type: New Feature
> Components: Container, Other, Struts Portlet, Components Core, Assembly/Configuration
> Versions: 2.0-M1
> Reporter: Peter Meier
> Attachments: jetspeed-2-diff.zip, portlet-event.zip, portlet-events-demos.zip
>
> As already announced elsewhere I would like to submit a working solution for inter-portlet communications between portlets that do not belong to the same portlet application.
> The implemented portlet communication is not part of JSR168 and therefore a proprietary extension. It utilises the JSR168 portlet API, though. Inter-portlet communication is achieved through portlet event notifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org