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]

Portlet API comparison white paper: JSR 168 Java Portlet Specification compared to the IBM Portlet API

Stefan Hepper, WebSphere Portal Programming Model Architect, EMC
Author photo
Stefan Hepper is the architect responsible for the WebSphere Portal programming model and public APIs. He was co-leader of the Java Portlet Specification JSR 168. He also started the Pluto project at Apache, which provides the reference implementation of JSR 168. Stefan has delivered a number of lectures at international conferences, such as JavaOne, published various papers, and is co-author of the book Pervasive Computing (Addison-Wesley 2001). His research interests are component-based software architectures, pervasive infrastructures, and, of course, portals and portlets. 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)

Summary:  Portlet developers can read this paper to see a side-by-side comparison of the Portlet API provided by IBM with the Websphere Portal V5.x product, and the JSR 168 Java Portlet Specification, which is developed through the Java Community Process. The paper describes the conceptual differences between the two APIs, provides specific examples, and discusses the relationship to the Web Service for Remote Portlets (WSRP) service. It also offers advice for programming portlets with the IBM Portlet API so you can easily convert them to the JSR 168 API.

Date:  28 Jun 2004
Level:  Intermediate

Activity:  1876 views
Comments:  

Portlet developers can read this paper to see a side-by-side comparison of the Portlet API provided by IBM with the Websphere Portal V5.x product, and the JSR 168 Java Portlet Specification, which is developed through the Java Community Process. The paper describes the conceptual differences between the two APIs, provides specific examples, and discusses the relationship to the Web Service for Remote Portlets (WSRP) service. It also offers advice for programming portlets with the IBM Portlet API so you can easily convert them to the JSR 168 API.

This paper is provided As-Is. A reviewed, edited, and summarized version, which was also written by Stefan Hepper (published December 2003), is available on developerWorks; it is called Comparing the JSR 168 Java Portlet Specification with the IBM Portlet API.


Download

DescriptionNameSizeDownload method
Article in PDF format 0406_hepper-Whitepaper-JSR168-WP5PortletAPI-comparison.pdf .9 MBFTP|HTTP

Information about download methods          Get Adobe® Reader®


Biography

Author photo developerWorks Professional author level

Stefan Hepper is the architect responsible for the WebSphere Portal programming model and public APIs. He was co-leader of the Java Portlet Specification JSR 168. He also started the Pluto project at Apache, which provides the reference implementation of JSR 168. Stefan has delivered a number of lectures at international conferences, such as JavaOne, published various papers, and is co-author of the book Pervasive Computing (Addison-Wesley 2001). His research interests are component-based software architectures, pervasive infrastructures, and, of course, portals and portlets. Stefan received a Diploma of Computer Science from the University of Karlsruhe, Germany, and in 1998 he joined the IBM Böblingen Development Laboratory.

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=23585
SummaryTitle=Portlet API comparison white paper: JSR 168 Java Portlet Specification compared to the IBM Portlet API
publish-date=06282004
author1-email=sthepper@de.ibm.com
author1-email-cc=flanders@us.ibm.com,debcot@us.ibm.com