Relation to cooperative portlet wiring
We can use both live text elements and cooperative portlet wires to exchange data between portlets on a page.However, the execution flow for both methods is different:
- Flow for cooperative portlet wiring:
- Flow for click-to-action
- The source portlet renders a source HTML tag containing the source data.
- The user clicks on the source element to open a menu and selects the target action from the menu
- The source data is sent to the server where a target portlet action is executed with the source data.
The following table lists differences that will help you decide which method for data exchange is appropriate for the application:
Click to action Portlet wires Is based on dynamic presence of targets on a page. Is based on static administrator-defined wires. Triggers a single target selected from a menu. Triggers all defined targeto that have been wired up. Can only handle string data. Can pass complex data types.
- We can write portlets that support both methods; any portlet action declared in a cooperative portlet WSDthat defines an input parameter is available as a target for both click-to-action and portlet wiring. For sources, we can add a preference that lets the administrator control whether click-to-action live text should be emitted, as demonstrated by the cooperative portlet JSR shipping example.
- We can also combine both methods: a target action that is triggered by click-to-action can have wires attachethat will propagate to other portlet actions on the server within the same request. consequently, a single click-to-action menu selection can trigger multiple portlet actions on the server.
Parent Live text for click-to-action
Related:
Live text formats
Integrate click-to-action targets with the person menu
Comparison of the new features with click-to-action in IBM portlets
Portlet communication