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.
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.
|For WebSphere Portal V5.02||0403_hepper-JSR168_BestPractices.pdf||410 KB||FTP|HTTP|
|For WebSphere Portal V22.214.171.124||0403_hepper-JSR168_BestPractices-V126.96.36.199.pdf||435 KB||FTP|HTTP|
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.
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.