Home
Deciding which API to use
The IBM portlet API extends the servlet API and many of the main interfaces (request, response, session). JSR 168 API does not extend the servlet API, but shares many of the same characteristics. JSR 168 leverages much of the functionality provided by the servlet specification, such as...
- deployment
- class loading
- Web applications
- Web application life cycle management
- session management
- request dispatching
For new portlets, consider using JSR 286 to take advantage of its additional capabilities. If you cannot use JSR 286 for some reason, consider JSR 168 when that functionality is sufficient for the portlets, or when the portlet is expected to be published as a Web Service for Remote Portlets (WSRP) service. WSRP is another portal-based standard used to integrate the presentation of remote portlets provided as Web services into the local portal page. The concepts in JSR 168 and WSRP have been aligned to allow JSR 168 portlets to be published as Web services. Some of these concepts include portlet modes and states, URL and name space encoding, and the handling of transient and persistent information.