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 168 compliant portal.
In this article, we will further our study of portlet portability. In
particular, we will focus our discussion on the Web services for remote
portals (WSRP) standard. The vision of WSRP is to allow portlets to be
exposed as Web services. The resulting Web service will be user-facing and
interactive. Unlike traditional data-oriented Web services, a WSRP-compliant
We... (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)
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)