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):||12 August 2005|
|PDF File Size:||20.38 Mb|
|ePub File Size:||11.16 Mb|
|Price:||Free* [*Free Regsitration Required]|
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.
For those who want to adopt portals certainly need many and variety of jsd to deploy and run.
A portlet container is not responsible for aggregating the content produced by the portlets; the portal itself handles aggregation. A Portlets Catalog is a set of portlets that are ready-to-use components for enterprise portals.
Some examples of portlet applications are e-mailweather reportsdiscussion forumsand news. These components will comprise -but they will not be restricted to-: 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.
The expert group will ensure this specification draws appropriately from such projects and products and that it will be based on open standards.
The Portlet specification will restrict the use of functions provided by the Servlet API to a subset that makes sense for apo providing fragments of a markup page. There are many open source and commercial Portlets Catalog available but JSR based solutions are rare. The Java Portlet Specification V1. For deployers, it’s easy to keep a single set of solution and deploy it on many.
JSR specifications offer suitability to the developers to reuse the code to maintain a set of Portlett compliant portlets. A portlet can aggregate integrate and personalize content from different sources within a web page. Some of these concepts include portlet modes and states, URL and namespace encoding, and the handling of transient and portet information.
The Portlet specification is required to achieve interoperability between Portlets and Java-based Portal servers or other web applications that implement the specification.
The TCK will be managed by Sun and will be available to independent implementors with no requirements to also license or use the RI. The Portlet specification will define the different components for Portal Computing, their interaction, lifecycle and semantics.
Portlets are pluggable user interface software components that are managed and displayed in a web portalfor example an enterprise portal or a web CMS. The Portlet specification will be designed leveraging the following technologies: 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.
There will be no shared code requirements. Oracle 9i Portal http: Web Logic Portal 4. 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 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.
Different implementations are available today, the following list enumerates some of them: Here Portlets catalog are of use. A portlet responds to requests from a web client with and generates dynamic content.
The Java Community Process(SM) Program – JSRs: Java Specification Requests – detail JSR#
A portlet is managed by a portlet container. APIs and descriptors to support internationalization and localization are a fundamental design goal of this JSR. A JSR portlets catalog makes sure that portlets under this catalog may run on any standards—compliant Java portal server. In addition, APIs for vendor extensions, APIs for security, user customization and layout management will be considered.
For example, a proxy Portlet could be used to invoke a remote Portlet. It is understood that the subject of this JSR is already being addressed by Open Source projects and products from different vendors.
Java Portlet Specification
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.
Portlets are web components -like Servlets- specifically designed to be aggregated in the context of a composite page. 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.
For a description of the Portlet technology, refer to section 2.
Java Portlet Specification – Wikipedia
You can edit these new elements by clicking on the Portlet Deployment Descriptor that is created when you create a new portlet project. Hence a portlet or collection of portlets resembles a web-based application that is hosted in a portal. It will also address how the security and personalization is handled. Usually, many Portlets are invoked to in the single request of a Portal page. Views Read Edit View history. Retrieved from ” https: Java enterprise platform Java specification requests Web portals.
Unsourced material may be challenged and removed.