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
personalization, single sign-on, and content aggregation from different
sources. It is the responsibility of a ... (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
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... (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 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 vi... (more)
Andrew Sweet serves as a senior solution architect for IBM’s WebSphere Services and is a frequent speaker and mentor around enterprise best practices and standards-based technologies such as J2EE and Web services. Andy also has served on the boards of several industry standards groups and technology councils, including OASIS WS-Security and UDDI, Web Services on WebSphere (WoW), IBM’s WebSphere Advisory Board, and Washington University’s Center for the Application of Information Technology program.
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
Ken Guiberson
