The Java Portlet Specification defines a contract between the portlet container and portlets and provides a convenient programming model for portlet developers. The Java Portlet Specification V1.0 was developed under the Java Community Process as Java Specification Request (JSR) 168.
The Java Portlet Specification V1.0 introduces the basic portlet programming model with:
- two phases of action processing and rendering in order to support the Model-View-Controller pattern.
- portlet modes, enabling the portal to advise the portlet what task it should perform and what content it should generate
- window states, indicating the amount of portal page space that will be assigned to the content generated by the portlet
- portlet data model, allowing the portlet to store view information in the render parameters, session related information in the portlet session and per user persistent data in the portlet preferences
- a packaging format in order to group different portlets and other J2EE artifacts needed by these portlets into one portlet application which can be deployed on the portal server.
Portal servers
JSR 168 compliant portal servers:
- IBM WebSphere Portal
- Sun Java System Portal Server
- BEA Weblogic Portal
- Oracle iAS Portal
- JBoss Enterprise Portal Platform
- Liferay Portal
- Vignette App Portal
- eXo Platform Portal
- SAP Enterprise Portal
- TIBCO PortalBuilder
- Apache Pluto
- JetSpeed Portal ver.2
- uPortal
- OpenPortal
See also
External links
- JSR 168
- JSR 286 (version 2.0 of the Java portlet specification)
- JSR 168 Open Source Reference Implementation at Apache
- Open source JSR 168/WSRP community at http://java.net
- Dynamic SOAP Portlet, for dynamic integration of SOAP services in JSR-168 portals