The Web Service for Remote Portlets (WSRP) specification proposed by OASIS defines presentation-oriented Web services. The difference from traditional data-oriented Web services is that WSRP services provide markups that can be used directly for rendering while data-oriented services provide only data. If services are facing end-users, the data needs further processing before it can be rendered properly for them. WSRP makes it possible for service providers to develop and maintain independent services without re-designing user interfaces (UI) at the service client side. This greatly alleviates the hard work needed in constructing end-user focusing applications like Web portals.

Although WSRP depicts a beautiful blueprint for future portal development, according to our previous investigation on open-source portal frameworks including eXo platform, Liferay, StringBeans and uPortal (plus WSRP4J), there are many interoperability issues between different portal frameworks. Even with producer and consumer from the same portal framework almost none of the WSRP implementations is fully functional. Therefore in this talk, a deep look at WSRP4J, the Apache WSRP 1.0 implementation will be given.

Topic revision: r1 - 11 Jul 2006 - RobAllan
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback