The Java Specification Request for the Portlet Specification (a.k.a. JSR
168), articulated by the Java Community Process in October 2003, aims to
provide a standard for portlets that the portal arena has lacked. Portlets
that are written to the JSR 168 spec will be deployable to any JSR
168-compliant portal.
The spec in essence defines a contract between a portlet and the portlet
container that powers it. Areas covered by the APIs defined in the
specification include topics such as aggregation, personalization,
presentation, and security. As these concepts are core to the portal realm,
they needed to be addressed by a spec in order to enable interoperability
between portlets and portals.
A portal is a Web application that typically provides end users with
personalizat... (more)
Portlets constitute interactive Web application components whose presentation
markup is aggregated and displayed by a portal server like WebSphere Portal.
In a previous WebSphere Journal article, we introduced you to the Java
Specification Request for the portlet specification (JSR 168), which lays out
the plans for a standard for portlets that will enable them to be deployed to
any JSR ... (more)
The Java Specification Request for the Portlet Specification (a.k.a. JSR
168), articulated by the Java Community Process in October 2003, aims to
provide a standard for portlets that the portal arena has lacked. Portlets
that are written to the JSR 168 spec will be deployable to any JSR
168-compliant portal.
The spec in essence defines a contract between a portlet and the portlet
contai... (more)