WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Receiving property values between cooperative portlets

In order for cooperative portlets to receive property values, corresponding property parameters must be registered programmatically. Make sure the source portlet has the appropriate output parameters specified. These output parameters will become the properties to be sent at runtime. To see an example of how to register property values programmatically, see the Destination Guide example in Included cooperative portlet samples.

For IBM portlets, instead of delivering property changes through portlet action invocations, changes may also be delivered using either the setProperties() method of the PropertyListener interface or the actionPerformed() method. If the portlet is a listener, then only setProperties() is called. This can happen if the target end of the wire connects to a target property, rather than a target parameter. In this event, the property broker may deliver multiple property values in a single invocation of setProperties(). The same property may appear multiple times in the array passed. Also, setProperties() is only invoked during the event phase, and all property changes which the portlet is eligible to receive are guaranteed to be delivered by the end of the event phase (as indicated by the invocation of the endEventPhase() callback in the EventPhaseListener interface).

If the portlet is not a listener, then actionPerformed() is called to deliver the property value, and setProperties() is not used.

 

Related Links