Sharing information between IBM portlets and JSR 168 portlets with WebSphere Portal V5.1

Create a customized property sharing portlet service

From the developerWorks archives

Stefan Hepper and Jerry Zheng

Date archived: July 17, 2017 | First published: February 15, 2006

The capability of portlets to exchange information (also called inter-portlet communication or cooperative portlets) is powered by the property broker in WebSphere Portal. The WebSphere Portal V5.1.0.1 property broker does not support inter-communication between IBM portlets and JSR 168 portlets because they run within separate portlet containers. This article shows you how to write a custom portlet service to enable legacy IBM portlets and JSR 168 portlets to share information as properties. You also see how to manage the life cycle of a shared information property in a distributed environment, using the dynamic WebSphere Application Server caching feature. To get the most out of this article, you should have a good understanding of Java portlet programming and a basic understanding of the WebSphere Portal portlet service feature. See Resources for links to information that can help you get this foundation.

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=103970
ArticleTitle=Sharing information between IBM portlets and JSR 168 portlets with WebSphere Portal V5.1
publish-date=02152006