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.
|Published (Last):||24 May 2015|
|PDF File Size:||1.96 Mb|
|ePub File Size:||9.25 Mb|
|Price:||Free* [*Free Regsitration Required]|
It is now hosted on SourceForge, so feel free to download the code to try it out or contribute your own enhancements.
It is expected that both specification leaders will fully share responsibilities associated with group leadership, including group communications, decision making, and agreeing to the business terms for the RI and TCK. This specification will establish a standard API for creating Portlets, thus avoiding porrtlets in Portal developers in a specific implementation and allowing Portlets developers to reach a wider audience while reducing their development efforts.
Allow any number of users to access portets in Documentum without specifying Documentum credentials. For details on deployment descriptors and other information, see “Introduction to JSR A portlet container is not responsible for aggregating the content produced by the portlets; the portal itself handles aggregation.
Expires after specified seconds The duration in seconds of the expiration cache.
Java Portlet Specification
Initialization Parameters Property Name Description Initialization Specifies the initialization parameters of the portlet. One of the most common public examples of a portal site is my.
The Portlet specification will restrict the use of functions provided by the Servlet API to a subset that makes sense for components 18 fragments of a markup page.
This first version of the Portlet specification will concentrate in the following design goals: It is an important goal that the design of the Portlet specification would allow implementations to support remote Portlet execution.
Select the Portlets tab, and then select the portlet from the Portlets list box. The Portlet Deployment Descriptor editor opens. This would limit the frequency of the queries against the content source. There will be no shared code requirements.
Now, as portal vendors begin to support the Java Specification Request http: A portlet container runs portlets and provides them with the required runtime environment.
The abstract ContentSource class Listing Three is the start of the content-retrieval process. Table 1 presents the results of an informal poll of portal popularity that was conducted by Punit Pandey http: It also helps to reduce the load on servers.
Configuring JSR portlets
Portals that allow users to search for portlets based on keywords may use these keywords. In this case, we extend the javax.
Select a preference validator class Validator class Specify a class that implements the PreferencesValidator interface to validate the set of preference porflets in the PortletPreferences object. Portlets should use this role name to determine whether the authenticated user is included in an application security role.
Each Portlet produces a fragment of markup that it s combined with the markup of other Portlets, all within the Portal page markup. In some portals, like eXo, the portlets are even responsible for the portal navigation. Defines an expiration based caching mechanism. Then click on the section that jwr the values you want to edit.
What is JSR portlet specification and its advantages? | Web Portal Club
This is typically in the form of a document repository. There are no limits to the complexity of a portlet.
Client agnostic Support for multiple types of clients multi-device Simple Pprtlets API Support for Localization and Internationalization Hot deployment and re-deployment of Portal applications Declarative security same as to the mechanism found in Servlet and EJB specs Architected to support remote execution of Portlets The Portlet specification will be based on the Servlet specification.
For a description of the Portlet technology, refer to section 2.
JSR 168 IBM extension for cooperative portlets
This simple class acts as the broker for the actual content-source implementations. Unsourced material may be challenged and removed.
Simple to install and configure.