The goal of JSR (Java Specification Request) , the Portlet and a set of portlet APIs that address personalization, presentation, and. To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Portal computing addressing the areas of aggregation. The Java Portlet Specification V was developed under the Java Community Process as Java Specification Request JSR , and.

Author: Yozshukus Shakazahn
Country: Djibouti
Language: English (Spanish)
Genre: Literature
Published (Last): 15 January 2011
Pages: 22
PDF File Size: 2.92 Mb
ePub File Size: 19.87 Mb
ISBN: 199-5-97174-613-7
Downloads: 59296
Price: Free* [*Free Regsitration Required]
Uploader: Shabar

Hence a portlet or collection of portlets resembles a web-based application that is hosted in a portal.

Portlet APIs

WSRP is another portal-based standard used to integrate the presentation of remote portlets provided as Web services into the local portal page.

For new portlets, consider using JSR to take advantage of its additional capabilities. If this specification, porltet a future version of this specification, is included in a future version of a Java platform specification, this specification will remain available for use outside the platform specification, and will continue to be evolved outside the platform specification, unless both specification leads agree otherwise.

Click-to-Action cooperative behavior and portlet messaging are not supported in JSR Faces portlets. NOTE that this section has been updated since the original request. 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.

Views Read Edit View history.

A portlet container runs portlets and provides them with the required runtime environment. A portlet container is not responsible for ali the content produced by the portlets; the portal itself handles aggregation.


The Portlet specification will define a Portlet API that provides means for aggregating several content sources and applications front ends. Portlets would be grouped in a Portal Application by bundling them in a single WAR with a Portlet deployment descriptor file. Some of these concepts jjsr portlet modes and states, URL and namespace encoding, and the handling of transient and persistent information.

Java Portlet Specification – Wikipedia

Initially Java portal vendors had their own portlet development framework thus those portlets were confined to specific portal servers and couldn’t be deployed to the rest of the Java portals. Furthermore, the Servlet specification does not define URL-rewriting functions to allow the creation of links and actions targeted to a specific form within the fragment of a page Portlet markup fragment.

The Java Portlet Specification defines a contract between the portlet container and portlets and provides a convenient programming model for Java portlet developers. For a description of the Portlet technology, refer to section 2. These components will comprise -but they will not be restricted to-: JSR is the Java Portlet specification v2. A Portlets Catalog is a set of portlets that are ready-to-use components for enterprise portals. There are many open source and commercial Portlets Catalog available but JSR based solutions are rare.

However, it does not address aggregation, security and personalization. It will also address how the security and personalization is handled. Some examples of portlet applications are e-mailjse reportsdiscussion forumsand news. Types of portlet solution vertical domains and technology like collaboration, social networking, community, content management, utility, calendaring, HRM all are available in these catalogs.

The Portlet specification will restrict portler use of functions provided by the Servlet API to a subset that makes sense for components providing fragments of a markup page. A JSR portlets catalog makes sure that portlets under this catalog may run on any standards—compliant Java portal server.


JSR Portlet API FR

JSR specifications offer suitability to the developers to reuse the code to maintain a set of JSR compliant portlets. A portlet is managed by a portlet container. January Learn how and when to remove this template message. Some of its major features include: Here Portlets catalog are of use. Client agnostic Support for multiple types of clients multi-device Simple Portlet 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.

The Portlet specification is required to achieve interoperability between Portlets and Java-based Portal servers or other web applications that implement the specification. This section provides you with information that can help porttlet decide which API to use when you develop portlets. The expert group will ensure this specification draws appropriately from such projects and products and that it will be based on open standards. Identification Request Contributions Section 1.

Typically, following the desktop metaphora portal page is displayed as a collection of non-overlapping portlet windows, where each portlet window displays a portlet. The goal is to allow Portlets to be packaged into WAR files and deployed in a standard way on any server implementing the specification.