Skip to main content


developerWorks  >  WebSphere | Workplace  >

Best practices: Developing portlets using JSR 168 and WebSphere Portal

developerWorks

Level: Intermediate

Stefan Hepper (sthepper@de.ibm.com), WebSphere Portal Programming Model Architect, IBM
Marshall Lamb (mlamb@us.ibm.com), Senior Technical Staff Member, WebSphere Portal Architect, IBM

02 Mar 2004
Updated 14 Jun 2006

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 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 methodsGet Adobe® Reader®


About the authors

Stefan Hepper is the responsible architect for the WebSphere Portal, Workplace Client and Server programming model, and public APIs. He co-lead the Java Portlet Specification V 1.0 (JSR 168), and is now leading the V 2.0 (JSR 286). Stefan started the Apache Pluto project that provides the reference implementation for JSR 168. He has delivered lectures at international conferences such as JavaOne, has published various papers, and was co-author of the book Pervasive Computing (Addison-Wesley 2001) and the Portlets and Apache Portals (download manuscript, Manning 2005). Stefan received a Diploma of Computer Science from the University of Karlsruhe, Germany. He joined the IBM Boeblingen Development Laboratory in 1998.


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.




Rate this content


Please take a moment to complete this form to help us better serve you.



YesNoDon't know
 


 


12345
Not
useful
Extremely
useful
 


Back to top


Document options

Document options requiring JavaScript are not displayed

Discuss


Rate this content

Help us improve this content