Saturday, 17 March 2012

Working with portlet container in websphere application server 7.0-Part7

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 that are available in the JSR-286 Portlet Specification and indicates to what extent these optional features are available in WebSphere Application Server. 

Table 1. Optional features in the JSR-286 Portlet Specification
Container runtime options
The following container runtime options are supported:
  • javax.portlet.escapeXml
  • javax.portlet.servletDefaultSessionScope
  • javax.portlet.actionScopedRequestAttributes
Setting 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 JavaServer Pages (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.

No comments:

Post a Comment