Monday, March 15, 2010

Portlet Standards

This is a topic researched by me for the literature survey of our final year group project.


Over the past few years, portals have evolved rapidly in the Internet space. They have helped businesses aggregate secure and personalized content and applications to the Web.Portlets used by portals function as pluggable user-interface components that provide a presentation layer to information systems.

In the early days of portal development, little emphasis was placed on component interoperability or reuse. Why? Because portlet APIs for development or customization at that time were limited to a single portal product only.

To overcome these problems, the Portlet Specification was started to provide interoperability between portlets and portals.

Portlet Specification defines the contract between a compliant portlet container and portlets. It defines a common Portlet API and infrastructure that provides facilities for personalization, presentation, and security. This standardization allows for portability of portlets between portal implementations.


• Support multiple portal products. The compliant portlets can be deployed to all compliant portal frameworks without extensive engineering changes.
• Code re-usability.
• Creates a wider market opportunity for portal tools: IDE’s, test tools, performance measurement tools and reporting interfaces.
• Support all compliant portal servers without additional engineering and support costs.

Mainly there are two categories for portlet standards.

1. Java Portlet Specification (JSR168, JSR286)

No comments:

Post a Comment