- Best practices: Developing portlets using JSR 168 and WebSphere Portal V5.02
- Converting the WorldClock portlet from the IBM Portlet API to the JSR 168 portlet API
The other problem that seems to be occuring are portlets that appear to conform with the specification, that do not seem to run on different containers. I am still investigating this one but as portal vendors enhance their own versions of the specification, this problem could get bigger.
Unfortunally, there is no easy solution to this, since the initial specification is so light in functionality (think WebSphere Portal version 2.1). A hard decision needs to be made between portability and taking advantage of enhanced functionality. Vendors will face this issue the most as they attempt to deliver full featured portlets for use on multiple platforms, that interface with their own system. For customers who are building their own portlets it may not be as hard a choice as they strive to meet user requirements.