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 May 2016|
|PDF File Size:||20.46 Mb|
|ePub File Size:||7.47 Mb|
|Price:||Free* [*Free Regsitration Required]|
Java Portlet 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. Rational tools supports portlet development based on the JSR specification.
The Portlet specification will be designed leveraging the following technologies: Usually, many Portlets are invoked to in the single request apl a Portal page. Here Portlets catalog are of use. Articles needing additional references from January All articles needing additional references.
Typically, following the desktop metaphora portal page is displayed as a collection of non-overlapping portlet windows, where each 1668 window displays a portlet. 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.
A portlet can aggregate integrate and personalize content from different sources within a web page.
Also, it will define the minimum set of possible window states for a Portlet such as normal, minimized, maximized, etc. NOTE that this section has been updated since the original request.
The Java Community Process(SM) Program – JSRs: Java Specification Requests – detail JSR#
JSR specifications offer suitability to the developers to reuse the code to maintain a set porglet JSR compliant portlets. This page was last edited on 21 Novemberat Web Logic Portal 4. 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, events, public render parameters and resource serving.
Some of its major features include: Testing and debugging portlets. However, it does not address aggregation, security and personalization. For example, a proxy Portlet could be used to invoke a remote Portlet.
It will also address how the security jjsr personalization is handled. These components will comprise -but they will not be restricted to-: It also provides persistent storage mechanisms for the portlet preferences.
The Portlet specification is required to achieve interoperability between Portlets and Java-based Portal servers or other web applications that implement the specification.
APIs and descriptors to support internationalization and localization are a fundamental design goal of this JSR.
Some examples of portlet applications are e-mailweather reportsdiscussion forumsand news. 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.
JSR Portlet API FR
A portlet container is not responsible for aggregating the content produced by the portlets; the portal itself handles aggregation. 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. A JSR portlets catalog makes sure that portlets under this catalog may run on any standards—compliant Java portal server.
A portlet is managed by a portlet container. Like the Servlet specification, the Portlet specification will allow access to Enterprise Information Systems without imposing restrictions on the type of protocols.
Web Services for Remote Portlets. 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. Types of portlet solution vertical domains and technology like collaboration, social networking, community, content management, utility, calendaring, HRM all are available in these catalogs.
Exact details will be agreed early in the life of the JSR and communicated to expert group members. Hence a portlet or collection of portlets resembles a web-based application that is hosted in a portal.
JSR leverages much of the functionality provided by the servlet specification, such as deployment, class loading, Web applications, Web application life cycle management, session management, and request dispatching.
A Java portlet resembles a Java Servletbut produces fragments rather than complete documents, and is not bound by a URL. JSR is the Java Portlet specification v3. Portlet standards platform independent application programming interfaces that are intended to enable software developers to create portlets that can be plugged into any portal supporting the standards.