Sample flow of cooperative portlet interaction

 

Sample flow of cooperative portlet interaction

 

+

Search Tips   |   Advanced Search

 

This topic contains the request-response flow of a cooperative portlet.

 

Standard portlets

This example assumes that wires already exist between the source and target portlets.

  1. The portlets are deployed. The WSDL file is processed and actions and properties are registered with the portal runtime.

  2. During the render phase of a request cycle, the portlet container requests markup from portlets. The resulting page is returned to the browser.

  3. The user initiates an action, for example clicking on a submit form button.

  4. In the action phase, the portlet container receives the request and calls the source portlet's processAction(), which may generate output property values.

  5. The property broker transfers the property values to any wired targets by invoking the target actions associated with the wires.

  6. The target portlet processes these property values. Steps 4-6 may repeat.

  7. All action processing for all portlets on the page completes. Render processing begins.

  8. After all render callbacks are completed, the portal assembles the response page and returns it to the client.

 

IBM portlets

This example uses Click-to-Action as an illustration, but it is similar to the series of events in the programmatic or wired interaction scenarios.

Click-to-Action flow

  1. During portlet deployment, the WSDL file associated with the application portlet is processed and actions and properties are registered with the portal runtime.

  2. During the render phase of a request cycle, the portlet container requests markup from each portlet. This may result in JSPs associated with the portlets being processed. Any Click-to-Action tags in the JSPs result in calls to the property broker, which determines matching actions on the page based on type information, and generates additional markup to display the icon used to invoke the pop-up menu.

  3. After all render phase portlet callbacks have been completed, the portal assembles the response page and returns it to the client.

  4. The end-user may click on the icon for a source to view a menu of compatible actions on the page and select one.

  5. A new request containing the chosen source and action information is generated and sent to the portal.

  6. The portal core runtime delivers the action to the target portlet. This is intercepted by the wrapper, which may interact with the broker to further process the request before delivering the action to the target.

  7. Wires may be triggered as in the previous flow.

 

Related information