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):||24 June 2018|
|PDF File Size:||10.55 Mb|
|ePub File Size:||19.24 Mb|
|Price:||Free* [*Free Regsitration Required]|
Like the Servlet specification, the Portlet specification will allow access to Enterprise Information Systems without imposing restrictions on the type of protocols.
The Java Portlet Specification defines a contract between the portlet container and portlets and jsg a convenient programming model for Java portlet developers. A portlet container contains portlets and manages their life cycles.
Portlets that conform to the JSR specification are more portable and reusable, because they can be deployed to any JSR compliant portal.
For new portlets, consider using JSR to take advantage of its additional capabilities. The Portlet specification will define a Portlet API that provides means for aggregating several content sources and applications front ends. Java enterprise platform Porttlet specification requests Web portals.
A portlet is managed by a portlet container. A portlet container runs portlets and provides them with the required runtime environment.
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.
From Wikipedia, the free encyclopedia. The goal is to allow Portlets to be packaged into WAR files and deployed in a standard way on any server implementing the specification.
Retrieved from ” https: Identification Request Contributions Section 1. For those who want to adopt portals certainly need many and variety of portlets to deploy and run. This first version of port,et Portlet specification will concentrate in the following design goals: You can edit these new elements pportlet clicking on the Portlet Deployment Descriptor that is created when you create a new portlet project.
The Java Portlet Specification V1. 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.
However, it does not address aggregation, security and personalization. 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.
The Portlet specification will be designed leveraging the following technologies: These components will comprise -but they will not be restricted to-: A Java portlet resembles a Java Servletbut produces fragments rather than complete documents, and is not bound by a URL.
Click-to-Action cooperative behavior and portlet messaging are not supported in JSR Faces portlets. A portlet can aggregate integrate and personalize content from different sources within a web page.
This article needs additional citations for verification.
Portlets would be grouped in a Portal Application by bundling them in a single WAR with a Portlet deployment descriptor file. If this specification, or 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.
18 expert group will ensure this specification draws appropriately from such projects and products and that it will be based on open standards. Testing and debugging portlets.
It is understood that the subject of this JSR is already being addressed by Open Source projects and products from different vendors. Also, it will define the minimum set of possible window states for a Portlet such as normal, minimized, maximized, etc.
In addition, APIs for vendor extensions, APIs for security, user customization and layout management will be considered. Typically, following the desktop metaphora portal page is displayed as a collection of non-overlapping portlet windows, where each apj window displays a portlet. This section provides you with information that can help you decide which API to use when you porrtlet portlets.
The Portlet specification is required to achieve interoperability between Portlets and Java-based Portal servers or other web applications that implement the specification.