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):||6 February 2017|
|PDF File Size:||20.3 Mb|
|ePub File Size:||4.28 Mb|
|Price:||Free* [*Free Regsitration Required]|
This section provides you with information that can help you decide which API to use when you develop portlets. Portlet API Spec community draft: A Java portlet resembles a Java Servletbut produces fragments rather than complete documents, and is not bound by a URL.
Standard portlet API
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.
Oracle 9i Portal 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 specification will define a Portlet API that provides means for aggregating several content sources and applications front ends. A portlet container runs portlets and provides them with the required runtime environment.
Testing and debugging portlets. Different implementations are available today, the following list enumerates some of them: APIs and descriptors to support internationalization and localization are a fundamental design goal of this JSR. The Portlet specification will restrict the use of functions provided by the Servlet API to a subset that makes sense for components providing fragments of a markup page.
We anticipate a mixture of mailing list and occasional face to face or teleconference meetings.
Standard portlet API
You can edit these new elements by clicking on the Portlet Deployment Descriptor that is created when you create a new portlet project. It will also address how the security and personalization is handled.
JSR is a Java specification from the Java Community Process that has improved upon the JSR portlet API by providing additional capabilities, such as filters, ;ortlet, public render parameters and resource serving.
A portlet responds to requests from a web client with and generates dynamic content. For deployers, it’s easy to keep a single set of solution and deploy it on many. January Learn how and when to remove this template message.
JSR Portlet API FR
Creating portlet JSP files. Unsourced material may be challenged and removed. 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.
A portlet container receives requests from the portal to execute requests on the portlets hosted by it. The goal is to allow Portlets to be packaged into WAR files and deployed in a standard way on any server implementing the specification. For example, a proxy Portlet could be used to invoke a remote Portlet. 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.
An example is the Java Portlet Specification. It is understood that the subject of this JSR is already being addressed by Open Source projects and products from different vendors.
From Wikipedia, the free encyclopedia. The Expert group will consider functionality such as support for, parallel execution of Portlets within a single user request, logging, security and personalization.
WSRP is another portal-based standard used to integrate the presentation of remote poetlet provided as Web services into the local portal page. To be determined by the expert group, initial target is December Portlets are pluggable user interface software components that are managed and displayed in a web portal poftlet, for example an enterprise portal or a web CMS. There will be no shared code requirements. This first version of the Portlet specification will concentrate in the following design goals: Web Services for Remote Portlets.
The API will provide a URL-rewriting mechanism for creating links to trigger actions within a Portlet without requiring knowledge on how URLs are structured in the particular web application.
Each Portlet produces a fragment of markup that it s combined with the markup of other Portlets, all within the Portal page markup.
Usually, many Portlets are invoked to in the single request of a Portal page. Portlets are web components -like Servlets- specifically designed to be aggregated in the context of a composite page. For a description of the Portlet technology, refer to section 2.
A portal and a portlet container can be built together as a single component of an application suite or as two separate components of a portal application.