The Full Wiki

More info on Web Services for Remote Portlets

Web Services for Remote Portlets: Wikis

Advertisements
  

Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.

Encyclopedia

From Wikipedia, the free encyclopedia

Web Services for Remote Portlets (WSRP) is an OASIS-approved network protocol standard designed for communications with remote portlets.

Contents

Overview

The WSRP specification defines a web service interface for interacting with presentation-oriented web services. Initial work was produced through the joint efforts of the Web Services for Interactive Applications (WSIA) and Web Services for Remote Portlets (WSRP) OASIS Technical Committees. With the approval of WSRP v1 as an OASIS standard in September, 2003, these two technical committees merged and continued the work as the Web Services for Remote Portlets (WSRP) OASIS Technical Committee.

Scenarios that motivate WSRP functionality include:

  • content hosts, such as portal servers, providing portlets as presentation-oriented web services that can be used by aggregation engines;
  • content aggregators, such as portal servers, consuming presentation-oriented web services provided by portal or non-portal content providers and integrating them into a portal framework.

Implementation

The WSRP specification does not make any statements as to implementation. Java's portlet specification, JSR 168, and WSRP are not competing technologies. JSR 168 may be used to define a portlet, and WSRP may be used to define a portlet's operations to remote containers. JSR 168 portlets and WSRP may be used together to define a portlet and to provide remote operations. Similarly, .NET portlets may be created for use with WSRP. Interoperability between JSR 168 and .NET WSRP implementations has been demonstrated.

There are several WSRP implementations to assist developers. Apache WSRP4J is an Apache Incubator subproject spearheaded by IBM with the stated goal of "kick starting the broad adoption" of WSRP. WSRP4J was designed to assist in the development and deployment of WSRP v1 services. WSRP4J remains in incubator status, primarily due to patent concerns revolving around the WSRP specification. Given WSRP4J's incubator status, the project does not produce formal releases.

The OpenPortal WSRP project's goal is to create a high quality, enterprise-class WSRP v1 producer and consumer with an associated developer community. OpenPortal released a stable, tested build in April, 2007.

The eXo Platform project, provides an implementation of WSRP 1 and 2, producer and consumer using eXo Portal and eXo Portlet Container.

The current release, WSRP v1, provides a limited interoperability platform. Further versions of WSRP v1 were abandoned so that effort could be concentrated on WSRP v2. WSRP v2 will augment the initial standard with cross-portlet coordination and access management features. This major update to the standard will permit for a more useful integration of multiple of content sources, regardless of whether they are local or remote, into a new web application. In addition, WSRP v2 may support some subsets of Web 2.0 technologies, such as AJAX and REST, without requiring them. WSRP v2 was approved by OASIS on April 1st, 2008.

See also

External links

Advertisements

Advertisements






Got something to say? Make a comment.
Your name
Your email address
Message