+

Search Tips   |   Advanced Search

Portlet aggregation using JSPs


The aggregation tag library generates a portlet aggregation framework to address one or more portlets on one page If we write JSPs, we can aggregate multiple portlets on one page using the aggregation tag library. This tag library does not provide full featured portal aggregation implementation, but provides a good migration scenario if we already have aggregating servlets and JSPs and want to switch to portlets.

To allow the customer to create a simple portal aggregation, the aggregation tag library also provides the following features.

The aggregation tag library and JSPs that use the aggregation tag library will only work with the WAS portlet container implementation because the protocol between the tags and the container is not standardized.

The following diagram depicts how an HTML page would look like and what tags are used in order to create the page.

See Aggregation tag library attributes for information on the aggregation tag library attributes.

When you use the aggregation tag library, set the portletUrlPrefix attribute of the init tag to the aggregating application. we need to:

When aggregating multiple portlets on a single page, special care must be used with the naming conventions of form attribute names in the portlets.

Because the portlets are all on the same page, they all share the same HttpServletRequest.

When one portlet is viewed the entire page is refreshed and form data is re-posted. Therefore, if there are multiple portlets that are aggregated on a single page with the same form attribute names, there could be logic corruption when form data is re-posted.



Subtopics


Aggregation tag library attributes
Example: Using the portlet aggregation tag library

 

Related tasks


Task overview: Managing portlets

 

Related


Portlet container settings