Refreshing individual portlets and preferences using Single Portlet Refresh in WebSphere Portal V6.0.1

From the developerWorks archives

Stefan Behl and Stephan Hesmer

Date archived: July 19, 2017 | First published: December 05, 2007

Learn how to use a new feature called "Single Portlet Refresh" to improve your users' experience with your portal interface. Single Portlet Refresh was introduced in IBM WebSphere Portal Version 6.0.1 as an extension to the rendering model. First, you get an overview of the Ajax programming model in which portlets can leverage either servlets or portlets as a backend. Then, you learn how and when to use Single Portlet Refresh, as well as its limitations.

This article is for Java™ portlet programmers who are already familiar with the Java Portlet API as well as with API extensions offered by WebSphere Portal, such as the Navigational State SPI and Portal Model SPI. See Resources for links to related information that can help you to gain this knowledge.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Middleware
ArticleID=273102
ArticleTitle=Refreshing individual portlets and preferences using Single Portlet Refresh in WebSphere Portal V6.0.1
publish-date=12052007