Cooperative portlets overview
Cooperative portlets communicate using portlet actions, where each action on a portlet can be associated with...
- A single input property
- Zero or more output properties
An additional WSDL deployment descriptor...
- Defines which portlet actions are enabled for communication.
- Provides information about how the property value is transferred to or from the action, for example as...
- request attribute
- JSR 168 render parameter.
Cooperative portlets do not require extra APIs for communication, but can use the same interfaces that handle normal action processing. Action processing in a target portlet often does not actually need to distinguish between an action initiated by a portlet URL and an action initiated by the transfer of a property value from another portlet.
Cooperative portlet WSDLs are not evaluated for JSR 286 portlets, and therefore JSR 286 portlets do not support this model of re-using portlet actions for portlet communication.
Packaging considerations for cooperative portlets
Cooperative portlets that the IBM portlet API require that you add a generic wrapper portlet around your actual portlet class. This means that you need to package an additional library for this wrapper into each IBM cooperative portlet WAR file. The wrapper is required to intercept calls to the portlet and trigger portlet communication activity.
In the case of standard portlets, the function of the wrapper is provided through a portlet filter, and no extra runtime code has to be included in the portlet WAR file. Here is a sample portlet.xml.
Parent topic
Cooperative portlets
Related concepts
Cooperative portlet programming model
Packaging, deploying and compiling cooperative portlets
Related reference
WSDL reference for cooperative portlets