Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Best practices: Developing portlets using JSR 168 and WebSphere Portal

Stefan Hepper, WebSphere Portal Programming Model Architect, EMC
Stefan Hepper is the responsible architect for the WebSphere Portal and Workplace programming model and public APIs. He co-led the Java Portlet Specification V1.0 (JSR 168) and is now leading the V2.0 (JSR 286) effort. Stefan received a Diploma of Computer Science from the University of Karlsruhe, Germany, and in 1998 he joined the IBM Böblingen Development Laboratory.
(An IBM developerWorks Professional Author)
Marshall Lamb (mlamb@us.ibm.com), Senior Technical Staff Member, WebSphere Portal Architect, EMC
Photo: Marshall Lamb
Marshall Lamb is a Senior Technical Staff Member and Software Architect for WebSphere Portal. He was previously the Chief Programmer for WebSphere Portal for several years. Marshall started in networking software development, working through the Host Integration product line, before moving into the Pervasive Software Division (WTP), and finally into Lotus Software with WebSphere Portal.

Summary:  This paper describes best practices for designing and developing portlets that conform to the JSR-168 standard, and which leverage the IBM WebSphere Portal infrastructure for JSR 168.

Date:  14 Jun 2006 (Published 02 Mar 2004)
Level:  Intermediate

Activity:  8743 views
Comments:  

This paper describes best practices for designing and developing portlets that conform to the JSR-168 standard, and which leverage the IBM WebSphere Portal infrastructure for JSR 168.

Summary

The first release of JavaTM Portlet Specification, JSR 168, by the Java Community Process, provides a standard for interoperability between portlets and portals. Developers who create portlets which conform to this specification greatly increase the portability and potential for reuse of their portlets, and they can deploy these portlets to any JSR 168 compliant portal. WebSphere Portal V5.02 supports JSR 168.

This document is a collection of best practices for portlet developers who want their portlets to conform to, and to leverage the IBM® WebSphere® Portal infrastructure for JSR 168. You can use these coding guidelines when designing and developing JSR 168 portlets for WebSphere Portal. It is not a primer for portlet development, because it does not address the fundamentals of portlet programming. Instead, use it as a checklist during design and code reviews to help promote consistent and quality portlet implementations.

For an introduction to JSR 168, see Comparing the Java Portlet Specification JSR 168 with the IBM Portlet API. For additional details, see the JSR 168 Portlet Specification.


Downloads

DescriptionNameSizeDownload method
For WebSphere Portal V5.020403_hepper-JSR168_BestPractices.pdf410 KBFTP|HTTP
For WebSphere Portal V5.1.0.10403_hepper-JSR168_BestPractices-V5.1.0.1.pdf435 KBFTP|HTTP

Information about download methods          Get Adobe® Reader®


Biographies

Stefan Hepper developerWorks Professional author level

Stefan Hepper is the responsible architect for the WebSphere Portal and Workplace programming model and public APIs. He co-led the Java Portlet Specification V1.0 (JSR 168) and is now leading the V2.0 (JSR 286) effort. Stefan received a Diploma of Computer Science from the University of Karlsruhe, Germany, and in 1998 he joined the IBM Böblingen Development Laboratory.

Photo: Marshall Lamb

Marshall Lamb is a Senior Technical Staff Member and Software Architect for WebSphere Portal. He was previously the Chief Programmer for WebSphere Portal for several years. Marshall started in networking software development, working through the Host Integration product line, before moving into the Pervasive Software Division (WTP), and finally into Lotus Software with WebSphere Portal.

Comments



Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=128635
SummaryTitle=Best practices: Developing portlets using JSR 168 and WebSphere Portal
publish-date=06142006
author1-email=sthepper@de.ibm.com
author1-email-cc=
author2-email=mlamb@us.ibm.com
author2-email-cc=