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.
|Published (Last):||23 March 2009|
|PDF File Size:||6.76 Mb|
|ePub File Size:||14.28 Mb|
|Price:||Free* [*Free Regsitration Required]|
A portal and a portlet container can be built together as a single jwr of an application suite or as two separate components of a portal application. 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 Community Process(SM) Program – JSRs: Java Specification Requests – detail JSR#
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 Apl specification. The Expert Group will evaluate defining a Credential mapping service to allow the Portal application to access resources in other applications not supporting the notion of distributed sessions- on behalf of user.
Portlet API Spec community draft: APIs and descriptors to support internationalization and localization are a fundamental design goal of this JSR. The Java Portlet Specification defines a contract between the portlet container and portlets and provides a convenient programming model for Java portlet developers.
We anticipate a mixture of mailing list and occasional face to face or teleconference meetings. Click-to-Action cooperative behavior and portlet messaging are not supported in JSR Faces portlets.
A portlet container contains portlets and manages their life cycles. Different implementations are available today, the following list enumerates some of them: Exact details will be agreed early in the life of the JSR and communicated to expert group members. Retrieved from ” https: There will be no shared code requirements.
In addition, APIs for vendor extensions, APIs for security, user customization and layout management will be considered.
A portlet can aggregate integrate and personalize content from different sources within a web page. WSRP portllet another portal-based standard used to integrate the presentation of remote portlets provided as Web services into the local portal page. This design would not address the transport protocol for the remote execution of Portlets, leaving to the specific Portal implementations the support for Portlet remote execution.
The Java Portlet Specification V1.
Java Portlet Specification – Wikipedia
The expert group will ensure this specification draws appropriately from such projects and products and that it will be based on open standards.
January Learn how and when to remove this template message. A Portlets Catalog is a set of portlets that are ready-to-use components for enterprise portals.
For a description of the Portlet technology, refer to section 2. This article needs additional citations for verification. The Portlet specification is required to achieve interoperability between Portlets and Java-based Portal servers or other web applications that implement protlet specification.
Portlets would be grouped in a Portal Application by bundling them in a single WAR with a Portlet deployment descriptor file.
JSR is the Java Portlet specification v2. Some of its major features include: Identification Request Contributions Section 1.
For new portlets, consider using JSR to take advantage of its additional capabilities. A portlet is managed by a portlet container.