Issue Details (XML | Word | Printable)

Key: JS2-208
Type: New Feature New Feature
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Unassigned
Reporter: Peter Meier
Votes: 2
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Jetspeed 2

Inter-portlet Communication

Created: 11/Feb/05 05:51 AM   Updated: 25/Sep/08 11:00 PM
Return to search
Component/s: Assembly/Configuration, Components Core, Container, Other, Struts Portlet
Affects Version/s: 2.0-M1
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
Zip Archive Licensed for inclusion in ASF works jetspeed-2-diff.zip 2005-02-11 05:53 AM Peter Meier 252 kB
Zip Archive Licensed for inclusion in ASF works portlet-event.zip 2005-02-11 05:53 AM Peter Meier 373 kB
Zip Archive Licensed for inclusion in ASF works portlet-events-demos.zip 2005-02-15 09:45 AM Peter Meier 5.31 MB

Resolution Date: 25/Sep/08 11:00 PM


 Description  « Hide
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.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Peter Meier made changes - 11/Feb/05 05:53 AM
Field Original Value New Value
Attachment portlet-event.zip [ 18930 ]
Attachment jetspeed-2-diff.zip [ 18929 ]
Peter Meier made changes - 15/Feb/05 09:45 AM
Attachment portlet-events-demos.zip [ 18969 ]
Michael Lipp made changes - 26/Oct/05 05:39 PM
Environment
Fix Version/s 2.0-POST [ 12310617 ]
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.
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.
Ate Douma made changes - 16/Sep/06 01:34 PM
Fix Version/s 2.1 [ 12310617 ]
Ate Douma made changes - 25/Sep/08 11:00 PM
Resolution Won't Fix [ 2 ]
Status Open [ 1 ] Closed [ 6 ]