The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

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.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

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

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: 11975 views
Comments:

Get the downloads

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 Java^TM 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

Description	Name	Size	Download method
For WebSphere Portal V5.02	0403_hepper-JSR168_BestPractices.pdf	410 KB	FTP\|HTTP
For WebSphere Portal V5.1.0.1	0403_hepper-JSR168_BestPractices-V5.1.0.1.pdf	435 KB	FTP\|HTTP