Experimenting with JSR 168 and WSRP

Experimenting with JSR 168 and WSRP

I recently started playing with portlets, mainly WSRP. It took me some time to figure out all the JSR 168 and WSRP terminology. It looked quite cool until I started using the tools. I used WebSphere portal UTE. My initial attempt to set up a WSRP channel between WebSphere and Liferay did not succeed because I assumed that it is going to be easy. It was not.

WebSphere portal UTE 5.0 does not have a complete GUI for enabling WSRP. So I pulled the WSRP4J code which uses maven 1.0 and not maven 2. I don’t know where this is specified and since I haven’t used maven before I wasted time trying to set it up with maven 2.

Now it looks like that I have to understand a slew of technology to really be very productive with WSRP and JSR 168. This could include Web service security, WSRP specification, JSR 168 specification, SOAP, WSDL and also the quirks of tools.

How do I understand this exception message if I don’t know the spec. ?

Consumer supplies a registrationHandle/registrationState pair that is not recognized by the Producer.

So I had to jump through several hoops just to view a simple WSRP portlet in the Swing consumer of WSRP4J.Aggregation of content using WSRP seems interesting. The following is the image of the WSRP4J Swing consumer showing a WebSphere portlet and its clone.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: