InfoQ

News

Web Services for Remote Portlets (WSRP) 2.0 Draft Available

Posted by Miko Matsumura on Jun 14, 2006 02:07 PM

Community
SOA
Topics
Portal/CMS,
WS Standards
Tags
OASIS
The OASIS Web Services for Remote Portlets TC recently has approved the latest revision 2.0 of the Web Services Remote Portlets as Committee Draft and approved the package for public review.

According to Subbu Allamaruaju, Staff engineer at BEA and a voting member of the technical committee, WSRP 2.0 is a major improvement over WSRP 1.0 and that the most important benefit of 2.0 is better user interaction - you can build more lively portlet applications with WSRP 2.0. The spec does improve upon WSRP 1.0 by adding a new operation to talk to portlets using technologies like AJAX. The WSRP TC already started working on developing a more comprehensive model for solving more complex AJAX use cases.

While WSRP 1.0 provided the basic plumbing for aggregating remote portlets, WSRP 2.0 makes the protocol more useful, and lets developers build more interactive applications using remote portlets.

Mr Allamaruaju went on to add "The key features that I'm most excited about are (a) coordination, which allows portlets to talk to each other in a loosely couple manner, (b) new interfaces to migrate portlets from environment to environment, which ease the pain of managing large remote portlet deployments, and (c) improved resource handling, which will address some of the AJAX use cases. There are a number of other changes in WSRP 2.0 which help clarify the spec better and make interoperability easier to archive."

As far as the relationship of JSR168 and JSR268 to this effort, Allamaruaju said "JSR-168/286 and WSRP have always been orthogonal. The Java specs define a programming model for portlets, while WSRP defines a remote protocol between portal applications and portlet containers. Although JSR-286 effort started later than WSRP 2.0, the JSR-286 EG (I'm member of this EG) is committed to developing a Java API that fully takes advantage of all WSRP 2.0 improvements. I'm happy to see that these specs are evolving together, which I think is a key requirement for the success of both."

Web Services for Remote Portlets Specification v2.0

The public review starts today, 14 June 2006, and ends 13 August 2006. The technical committee strongly encourages feedback from potential users, developers and others, whether OASIS members or not, for  improving the interoperability and quality of OASIS work.

You can find more information about the committee at its home page. Comments may be submitted to the TC by any person, by a web-form that can be reached either on that page, via the button marked "Send A Comment" at the top of that page, or using a web based form. Submitted comments (for this work as well as other works of that TC) are publicly archived. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members.

The specification document and related files are available in HTML format and PDF. The specification weighs in at about 200 pages. There are also XSD, WSDL interfaces available.

No comments

Reply

Exclusive Content

Rustan Leino and Mike Barnett on Spec#

Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.

10 Ways to Screw Up with Scrum and XP

Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.

Tips from a Top Sports Team Coach

This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.

SOA Governance: An Enterprise View

Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.

Developing Portlets using JSF, Ajax, and Seam (Part 2 of 3)

This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.

Scalability Worst Practices

This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.

Do the Hustle

Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.

Natural Laws of Software Development - Deriving Agile Practices

Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.