WSRP4J Project terminated

As of 2010-04-18, the WSRP4J (Incubating) project is terminated because of lack of community and interest

This site is kept online to provide documentation for legacy projects.

Welcome to WSRP4J


Integration of content and application into portals has been a task requiring significant custom programming effort. Portal vendors or organizations running portals had to write special adapter portlets to allow portals to communicate with the different applications and content providers to accommodate a variety of interfaces and protocols. The OASIS Web Services for Remote Portlets (WSRP) standard simplifies integration of remote applications/content into portals so that portal administrators can pick from a rich choice of services and integrate it in their portal without programming effort. As a result, WSRP becomes the means for content and application providers to provide their services to organizations running portals in a very easily consumable form.

The Apache WSRP4J open source project was initiated by IBM to facilitate quick adoption of the WSRP standard by content and application providers and portal vendors. They can use WSRP4J as a platform for developing and hosting WSRP compliant web services. The OASIS WSRP standard will enable thousands of portals to aggregate content from tens of thousands of content and application providers offering hundreds of thousands of user-facing, pluggable web services for millions of end users/devices.

We hope the WSRP4J project will kick start broad adoption of the WSRP standard and result in a large number of cool WSRP services running on free, open source Apache software.

Disclaimer WSRP4J is an incubated subproject under the sponsorship of the Apache Software Foundation's (ASF) Web Services project. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.