Blog Stats
  • Posts - 125
  • Articles - 0
  • Comments - 5
  • Trackbacks - 2

 

<< Architect School | Home | What's the Default Answer? >>

Sharepoint Web Services For Remote Portlets (WSRP)

In conversation, someone brought up a Java WSRP implementation and I thought it was an interesting idea. Web Services for Remote Portlets (WSRP) is an Oasis standard defines a set of interfaces and behaviors that allow you to embed content from as web service on your page but more importantly, it allow that content to be interactive with the web service so it's more than just pulling the HTML. Clicks and other events funnel back to the origional site so that you don't have to write the backend processing for those controls. This is an interesting idea so I started looking into it.

I was thinking on what would be required to write one, but it turns out that I don't have to since there's already one on GotDotNet for Sharepoint. There you can find the WSRP Consumer Web Part Toolkit and the WSRP Producer Web Service Toolkit.

It's a facinating idea and I can see real possibilities with it. The question that I have is - has anyone used this yet? How well does it work?

Print posted @ Sunday, January 07, 2007 12:58 AM

Feedback

# re: Sharepoint Web Services For Remote Portlets (WSRP)

Gravatar AVOID WSRP AT ALL COSTS! As an XML and web services guy, the idea of pushing UI via a web service is just disgusting. Web Services are made to push data, not UI, so that is a total bastardization of what web services are about.
Yes there is an implementation of WSRP on GotDotNet, but it is for 2003, not 2007. In SP 2007 you can be a consumer of WSRP (it is out of the box functionality), but you cannot be a publisher, and with the new model in 2007, it is just about impossible to write a WSRP publisher for it.
If you want to expose your data to other systems, do the right thing, and expose it via true web services, and not via WSRP. In the end, you will be better off for it. Yes, you will have to write the UI implementation code to render the web service as HTML, but the cost is a lot less than the hell you will go thru trying to work with WSRP.
Oh, yes, I’ve tried to work with WSRP between WebSphere and Sharepoint (both 2003 and 2007), with Sharepoint as both a consumer and a publisher for each portal, and in the end, pure web services was a heck of a lot easier, faster, and over all, better, especially once you get into security. In WSRP, they only recommend that you use WS-Security, and no one has implemented it, so they only use transport level security (HTTP).
1/7/2007 3:03 AM | Don Demsak

# re: Sharepoint Web Services For Remote Portlets (WSRP)

Gravatar Don,

Great comments and thank you for your great perspective as always.
I was having the same hang up about pushing UI especially since you're integrating it into your own UI and you can't guarantee that it will fit in from a consumer perspective. Additionally, it really limits the places that you are able to leverage that data.
I didn’t know about the security issues, but that’s also a showstopper in many cases. It’s also interesting that it’s harder to do the UI in your opinion. That kills the one reason that I would ever consider it.

Josh
1/7/2007 3:40 AM | Josh Holmes

# re: Sharepoint Web Services For Remote Portlets (WSRP)

Gravatar Hi,

I would like to implement the WSRP producer for SharePoint 2007. Kindly provide me with the references for the same.

Regards,
Mayur Joshi 5/13/2008 5:36 AM | Mayur

# re: Sharepoint Web Services For Remote Portlets (WSRP)

Gravatar Mayur,

I am wondering if you were able to implement WSRP producer for Sharepoint 2007.

Thanks.

11/21/2008 11:56 PM | Anas Mughal
Post a comment





 

 

 

 

Copyright © Josh Holmes