Portlet development reference

View important information and concepts related to portlet development.

Related

• Standard portlet API
• IBM Portlet API

• Markup guidelines
  View the guidelines for using HTML, WML, and cHTML markup in the portlet JSPs to provide a consistent, clean, and complete user interface.
• Build .ear and .war files
  We can run a configengine task to build an .ear file or a .war file from an expanded directory.
• Access the portlet session on the anonymous page
  View some pointers on handling portlet sessions in situations where portlets are placed on pages that do not require authentication.
• Deployment descriptors
  
• IBM portlet DTD tag reference
  Learn about the elements in the portlet deployment descriptors for the IBM Portlet API.
• JSP tags for standard portlets
  The standard portlet API defines several tags that can be used in portlet JSPs to get access to the portlet request and response and to generate URLs.
• JSP tags for IBM portlets
  Learn about the tags used by JSPs for IBM portlets. The IBM portlet API is deprecated. For new development work, use the Standard portlet API.
• Handling and visibility of request parameters in portlets
  Learn how the standard portlets and IBM portlets set request parameters for requests targeted to portlets. Acquire an understanding of the parameter visibility for standard portlets, IBM portlets, and the included JSPs or servlets.
• Detailed descriptions of the Struts WML tags
  Learn about the WML tags used by the portlets within the Struts Application Framework.
• Application extension registry
  WebSphere Portal provides an application extension registry which is equivalent to the application extension registry provided by IBM WAS. This registry allows any J2EE compliant application to define extension points for other applications to use, or to plug in to other extensible applications.

Parent: Develop portlets