WAS v8.5 > Develop applications > Develop Portlet applications > Portlet aggregation and preferences

Supported optional features of the JSR-286 Portlet Specification

The simple portal framework, which builds on top of the portlet container, is JSR-286-compliant. However, the WebSphere Application Server implementation supports a subset of the optional features in the JSR-286 Portlet Specification.

The following table lists the optional features available in the JSR-286 Portlet Specification and indicates to what extent these optional features are available in WAS.

Optional features in the JSR-286 Portlet Specification. The Availability column describes whether the product supports a specification feature.

Feature	Availability
Container runtime options	The following container runtime options are supported: javax.portlet.escapeXml javax.portlet.servletDefaultSessionScope javax.portlet.actionScopedRequestAttributes
Set the HTML head section elements using the MimeResponse.MARKUP_HEAD_ELEMENT property	This property is not supported as its setting does not have an effect.
Custom portlet modes and custom window states	The feature is supported, but without special treatment.
Portlet-managed modes	This feature is fully supported.
Dynamically setting the portlet title using the RenderResponse.setTitle(String) method	This feature is partially supported. You need to make use of this feature in a portlet document filter or an aggregation JSP file.
Dynamically setting the next possible portlet modes using the RenderResponse.setNextPossiblePortletModes(Collection<PortletMode>) method	This feature is not supported.
Expiration and validation-based caching	This feature is fully supported. You need to activate the portlet fragment caching and a cachespec.xml defined as a prerequisite.
Aliases in public render parameters	The aliases in public render parameters are supported in the PortletServingServlet servlet and the aggregation tag library.
Aliases and wild cards in eventing	These aliases and wild cards are not supported as setting these functions does not have an effect.

Subtopics

• Aggregation tag library attributes
  The aggregation tag library is used to aggregate multiple portlets on one page. This topic describes the attributes within the aggregation tag library.
• Example: Using the portlet aggregation tag library
  We can use the aggregation tag library to aggregate multiple portlets to have multiple and different content on one page. The library can be used by every JSP file that has been included by a servlet.

Related concepts:

Portlet container

Related information:

JSR 286 Portlet Specification

Introducing Java Portlet Specifications - JSR 168 and JSR 286

+

Search Tips   |   Advanced Search