Browse Prior Art Database

Method for creating and processing inter-portlet URLs in a remote portlet environment

IP.com Disclosure Number: IPCOM000191038D
Original Publication Date: 2009-Dec-14
Included in the Prior Art Database: 2009-Dec-14
Document File: 2 page(s) / 427K

Publishing Venue

IBM

Abstract

Disclosed is a method for creating and processing inter-portlet URLs on a producer in a remote portlet environment. The inter-portlet URLs may target other portlets that are provided by the same producer or remote portlets provided by other producers.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Method for creating and processing inter -portlet URLs in a remote portlet environment

A typical portal provides access to user specific information, applications and processes using local and remote information sources. It combines the aggregated applications and provides a unified presentation layer. Most of today's portal implementations provide a component model that allows plugging components referred to as Portlets into the portal infrastructure. Portlets, as defined by the Portlet specifications, are user-facing interactive web applications that render markup fragments. The content of a portlet is normally aggregated with content from other portlets to form a portal page.

Besides portlets locally executed on the Portal system another standard named WSRP (Web Services for Remote Portlets) introduced a mechanisms that allows dynamic integration of portlets executed on remote portal systems so called WSRP Producers into other WSRP Consumer portals. Remote portlets also provide markup fragments that combine data and presentation logic and that can be aggregated together with local portlets to form the content of a portal page. Usually the consumer portal communicates with the WSRP remote portlets using generic proxy portlet. Common advantages of remote portlets include aspects like integration of portlets across borders of different vendors portals independently of the technology used for the implementation and isolation of execution of alien code (portlets).

As part of its markup, a portlet often needs to create URLs that target 1) the portlet itself (portlet URL), 2) non-portlet resources such as JavaScripts, HTML documents, Servlets, Cascading Stylesheets etc (resource URL) or 2) other portlets (here called inter-portlet URL). While portlet URLs and resource URLs are defined in the WSRP specification and are implemented in prior art portals, there are no means in WSRP to create and process inter-portlet URLs. In prior art a portlet that is used as a remote portlet over WSRP therefore cannot create URLs that point to other portlets. This constrains the functionality of remote portlets and Portals and complicates integration.

The method is implemented on the producer and the consumer:

On the producer, a portlet creates a URL by invoking an API of the local portlet container or the local portal, which in turn invoke the URL generator component of the WSRP producer. This URL generator component creates an extended rewrite URL and inserts the according portlet handle and the producers w...