Standard portlet API
The Java Portlet Specification addresses the requirements of aggregation, personalization, presentation, and security for portlets running in a portal environment.Version 1.0 of the Java Portlet Specification was approved by the Java Community Process in October 2003 as JSR 168. The purpose of the specification is to solve the problem of portlet compatibility between portal servers offered by different vendors. Version 2.0 of the Java Portlet Specification extended the capabilities to include coordination between portlets, resource serving, and other advanced features. The final version 2.0 was approved by the Java Community Process in March 2008 as JSR 286.
WebSphere Portal includes a portlet run time environment that supports portlets developed according to the Java Portlet Specification, hereafter called standard portlets.
With WebSphere Portal there are some IBM specific parameters for portlets available. For more information about these parameters refer to the topic Deployment descriptors under the section Reserved parameter names.
For portlets conforming to JSR 286, WebSphere Portal also includes support for two-phase rendering.
The following topics provide specific information about the implementation of the standard portlet API within WebSphere Portal.
- Use two-phase rendering with JSR 286 portlets
For portlets conforming to JSR 286, IBM WebSphere Portal includes support for two-phase rendering, which allows portlets to set cookies and the HTTP headers and to change the portal page title dynamically.
Parent: Develop portlets
Related:
Portlet concepts
IBM Portlet API
Deployment descriptors
Related reference:
JSP tags for standard portlets
Related:
Convert IBM portlets (AIX IBM i Linux Solaris Windows)Java Portlet Specification JSR 286 (http://jcp.org/en/jsr/detail?id=286)
Java Portlet Specification JSR 168(http://jcp.org/en/jsr/detail?id=168)
Best practices: Developing portlets using JSR 168 and WebSphere Portal