+1 for it, but for 1.4M2 I think since 1.4M1 is planned to be released ASAP and we need it as stable as possible. Thanks -Vincent PS: Haven't looked at the code. On Mar 30, 2008, at 10:46 PM, Fabio Mancinelli wrote:
Dear all,
I've lost a bit the schedule of the 1.4M1 release, but I would like to propose the integration of the new version of the XMLRPC support that I've finished to write.
If it is too late for the 1.4M1 release I would like to propose its integration in the trunk for the next release.
This new version of XMLRPC is needed for enabling XEclipse to access advanced XWiki functionalities, notably Objects and Classes retrieval and edition.
The contribution consists of two parts:
1) A server side part that should replace the old com.xpn.xwiki.xmlrpc package. Differently from the previous version, the new one is completely coded against the XWiki API (com.xpn.xwiki.api) and doesn't use any other mechanism for performing operations (e.g., no calls to BaseObjects, etc.).
2) A client part that contains the data model and the tests. This client part is a mavenized-project of its own that should be used by all the clients wanting to access XWiki through XMLRPC. It is also used by the server-side part for what concerns the data-model (so the jar should also be available in the WEB-INF/lib)
Of course the API is a superset of the Confluence one, so we are still compatible.
In the attachments you will find all the commented code.
WDYT?
Cheers, Fabio
P.S.: The server-side package is called com.xpn.xwiki.xmlrpc3 which reflects the different iterations I did on this piece of code and the fact that I didn't touch the current implementation for "security reasons" :) Of course it should replace com.xpn.xwiki.xmlrpc once integrated.