Portlet communication

 

+

Search Tips   |   Advanced Search

 

1. Shared portlet state
   These communication methods are based on shared state between multiple portlets. This means that two or more portlets read and write to the same data.

2. Publish/subscribe message based communication
   These communication methods are based on directed communication links that pass information from a source portlet to a target portlet.

3. Special purpose techniques for data exchange
   IBM WebSphere Portal supports special purpose techniques for data exchange.

4. Portlet events
   Portlet events provide a powerful and flexible publish/subscribe mechanism for communication between JSR 286 portlets. They can be used to exchange complex data between portlets and to trigger portlet activity such as updates to back end systems. In the portal, they can also interoperate with other communication mechanisms such as Cooperative portlets and click-to-action.

5. Cooperative portlets
   Cooperative portlets represent an IBM specific API for publish/subscribe communication between portlets.

6. Interoperability between events and cooperative portlets
   By concept, cooperative portlets are similar to JSR 286 portlet events. Both concepts describe publish/subscribe communication patterns that are based on typed information that is published and received by portlets and propagated via communication links.

7. Event broker
   The portal event broker subsystem provides support for inter-portlet communication with active notifications using portlet events or the cooperative programming model.

8. Portlet wires
   Portlet Wires are used to direct the information flow between portlets that communicate using JSR 286 Portlet events or the WebSphere Portal Cooperative portlets API.

9. Public render parameters
   Public render parameters allow JSR 286 portlets to share navigational state information. They are specially useful for coordinating the multiple navigation or viewer portlets that display different information items that are all related to the same key. The portal stores all portlet render parameters, including public render parameters, as an encoded part of the current portal URL. Therefore public render parameters are correctly preserved by typical browser navigation actions such as Back button and bookmarking.

10. Known issues and restrictions with portlet communication
    

 

Parent topic

Developing portlets