portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Hawkins <jonathan.hawk...@hawkinsweb.co.uk>
Subject Re: [jira] Updated: (JS2-208) Inter-portlet Communication
Date Wed, 26 Oct 2005 10:03:27 GMT
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.
>>    
>>
>
>  
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message