Everyone, First off I wanted to let you guys know (many of you already do) that there are several important stakeholders in this project at this point who are using WSRP4J in their projects and care about its maturity and active maintenance. The ones that I'm familiar with are Sakai (www.sakaiproject.org), uPortal (www.uportal.org) and SunGard HES Luminis (www.sungardsct.com). I have been personally involved in using WSRP4J to implement a WSRP producer in Sakai (see http://bugs.sakaiproject.org/confluence/pages/viewpage.action?pageId=9675 for some slides) and to a much lesser extent in uPortal/Luminis use of WSRP4J to provide a WSRP consumer. I have made some patch contributions in the past to WSRP4J based on my work on Sakai and I'm anxiously looking forward to the refactored code that Diego is working on, because it significantly simplifies the ability to take things from the Sakai's implementation of WSRP producer and contribute the relevant aspects back. I will continue to submit bugs/patches as I run into them in course of my involvement with WSRP4J codebase in Sakai and uPortal/Luminis and would very much welcome the opportunity to be a committer. Regards, - Vishal -- Vishal Goenka SunGard SCT Lead Architect, Luminis Solutions www.sungardsct.com
