Portlet Window Manager

This page covers the following JIRA issues: UPT-11

Purpose

Window manager will maintain session-specific information for portlets being used by the user.

Main features

• Scope: PortletWindowManager should be session-scoped.
• PortletWindow instances should be obtained from the window registry (injected) and maintained in a map.
• Have methods to receive action and render parameters for different portlet windows
• Invoke PorletAction processing (on a container) upon receiving action parameters
• Maintain portlet render requests for the current rendering cycle for different portlets, and construct appropriate render requests when needed
• Return portlet render content (by invoking rendering procedure on the container) to the portlet content incorporation filter.
• Later on, implement asynchronous models of portlet render start/end(content retrieval)

Invoking action and render requests will require an http servlet request wrapper that will deliver request parameters relevant only for that portlet. An additional response wrapper will be used to record subsequent render request parameters from an action response, and IPortletRenderContent from render response.

These features are also described by the IPortletWindowManager interface in the org.jasig.portal.portlet.rendering package.