To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Updates to the Original Java Specification Request ( JSR). The Java platform provides an standard referred to as JSR that standarizes how portlets interact with portlet containers and ensures compatibility across. The Java Standardization Request (JSR ) defines a portlet specification, including a contract Enables interoperability among portlets and portals.

Author: Arakasa Moshicage
Country: Monaco
Language: English (Spanish)
Genre: Spiritual
Published (Last): 14 January 2009
Pages: 424
PDF File Size: 16.95 Mb
ePub File Size: 7.25 Mb
ISBN: 361-1-72549-549-6
Downloads: 82258
Price: Free* [*Free Regsitration Required]
Uploader: Ferg

A Map would have required a separate mechanism for ordering the keys. Select a preference validator class Validator class Specify a class that implements the PreferencesValidator interface to validate the set of preference values in the PortletPreferences object.

It the latter case, not only are you prevented from determining the root cause of the error, but if the error prevents access portlsts administrative links you may not be able to even remove the portlet from the page without uninstalling it.

Writing JSR portlets lets you become portal agnostic and lets vendors support a wider spectrum of platforms with little to no code changes. Several portals, such as eXo, Vignette, and IBM, support a custom “config” portlet mode to accomplish this very thing. There will be no shared code requirements.

A portlet container contains portlets and manages their life cycles. Its main goals were that the portlets be simple, client agnostic, and secure.

Portlet standards platform independent application programming interfaces that are intended to enable software developers to create portlets that can be plugged into any portal supporting the standards. The Expert group will consider functionality such as support for, parallel execution of Portlets within a single user request, logging, security and personalization.


Specify the following portlet information for each supported locale. Additional settings must also be provided using a deployment descriptor extension ibm-portlet-portal-ext. Values Initial default values of the preference.

JSR IBM extension for cooperative portlets

The transmission of the document contents to the client machine is handled through a servlet, ContentServlet Listing Portlete. These components will comprise -but they will not be restricted to-: They will be useful for gathering features and evaluating the effectiveness and shortcoming of each implementation. This presents a problem when you want to provide administrative functionality through a special view or page.

This specification will establish a standard API for creating Portlets, thus avoiding locking in Portal developers in a specific implementation and allowing Portlets developers to reach a wider audience while reducing their development efforts.

1688 one short title per locale is allowed. If you specify a security role which has been already defined in the web deployment descriptor you can select it from the list. It also helps to pirtlets the load on servers.

It is only shown in GUI tools. The document’s ID could then be relative to one or both of these values depending on how identifiers are managed in the source.

Developing JSR-168 Portlets

JSR specifications offer suitability to the developers to reuse the code to maintain a set of JSR compliant portlets. It will also address how the security and personalization is handled.

Typically, the portlet class is more complex as most portlets have multiple views view, edit, help, and so on and also have to handle user actions. Now, as portal vendors begin to support the Java Specification Request http: The Java Portlet Specification defines a contract between the portlet container and portlets and provides a convenient programming model for Java portlet developers.

The portlet class loads the Java Server Page JSP file that is, in turn, responsible for calling the content classes and displaying the folder contents. Because this portlet could be on a page with countless other portlets, we need to ensure that any problems we encounter do not bubble up and crash the entire page or possibly the entire portal server.


Always expires Caching is disabled for the portlet. Additional functionality such as workflow, search, versioning, and access control are also standard. For more information on the DocWay Published Folder, see http: The canonical name of the portlet selected in the Portlets list box. However, this could be enhanced to use a class loader to instantiate the implementing class based on a property file setting. Typically, following the desktop metaphora portal page is displayed as a collection of non-overlapping portlet windows, where each portlet window displays a portlet.

These could be done with as little as one class that extends the abstract ContentSource class. There are a couple of points to make about this JSP. Title The title that should be displayed in the title bar of this portlet.

This is the main entry point for the portlet and is the only class that the portal framework is really aware of for this project. A Java portlet resembles a Java Servletbut produces fragments rather than complete documents, and is not bound by a URL. Portlet Info Specify the following portlet information for each supported locale. Note that this title may be overridden by the portal or programmatically by the portlet.