Portal, V6.1
IBM Portlet API
The IBM Portlet API is being deprecated for WebSphere Portal V6.1, but is still supported. No new functionality will be added and IBM recommends you use the Standard Portlet API. These sections provide a brief description of the IBM Portlet API.
- Overview
- Portlet API concepts
- Elements of the Portlet API
- Core objects
- Listeners
- Configuration objects
- Miscellaneous objects
- Portlet events
- Deployment descriptors
- JSP tags of the IBM Portlet API
- Portlet API extensions
The Javadoc for the IBM Portlet API is available from the portal_server_root/doc/Javadoc.
Related information
- Overview
This topic provides an brief overview of the IBM portlet API. This API is deprecated and this topic is provided only to support portlets that have not been migrated to the standard portlet API.- Comparing the standard portlet API to the IBM portlet API
- Migrating from the IBM Portlet API
- Portlet API concepts
- Elements of the Portlet API
- Core objects
- Listeners
- Configuration objects
- Miscellaneous objects
- Portlet events
- JSP tags of the IBM Portlet API
- Portlet API extensions
- Portlet menus
- Writing a portlet filter
A portlet filter is an object that allows information flowing to or from a portlet (or filter) to be intercepted and manipulated. The object being filtered is intentionally left unaware of the filter's presence, allowing it to behave normally. Such an object can either be a portlet or another filter, thus allowing any number of filters to be applied to a single portlet, creating a filter chain (see the illustration below). While portlet filters can be used to manipulate data in any number of ways, one of their primary functions, for example, is to filter a portlet's input and results for use in secondary user interface environments (e.g., text terminals, PDAs, cell phones, and so on.). Because the portlet being filtered does not know about the filter, it can receive and respond to requests in a normal and robust fashion.
Parent topic
Developing portlets