Portlet container

 

+

Search Tips   |   Advanced Search

 

Overview

The portlet container is the runtime environment for portlets using the JSR 168 Portlet Specification, in which portlets are instantiated, used, and finally destroyed. The JSR 168 Portlet API provides standard interfaces for portlets. Portlets based on this JSR 168 Portlet Specification are referred to as standard portlets.

A simple portal framework is provided by the PortletServingServlet servlet, which registers itself for each Web application that contains portlets.

Use the PortletServingServlet servlet to directly render a portlet into a full browser page by a URL request and invoke each portlet by its context root and name.

To aggregate multiple portlets on the page, use the aggregation tag library.

The PortletServingServlet servlet can be disabled in an extended portlet deployment descriptor called the ibm-portlet-ext.xmi file.

 

Remote request dispatcher support for portlets

The remote request dispatcher support allows the invocation of portlets outside of the current JVM within an ND single core group environment. The request related data is passed to the remote JVM where the portlet is invoked. The response is transmitted back and processed on the local JVM. Thus it guarantees that URLs contained in the portlet markup are created according to the local portal context.


 

Related concepts

Portlets
Portlet URL addressability
Remote request dispatcher

 

Related tasks

Task overview: Managing portlets

 

Related Reference

Portlet container settings
Remote request dispatcher considerations

 

Related information

JSR 168 Portlet Specification
Introducing the Portlet Specification, Part 1
Introducing the Portlet Specification, Part 2
Introduction to JSR 168 - The Portlet Specification