Re: [xwiki-devs] Proposal: Breaking API changes in the XML-RPC implementation

Hello, In a previous message I explained that I will soon do breaking API changes in the XML-RPC implementation, but I was not explicit enough about. Here is what I plan to implement ASAP if everybody agrees: 1) Remove the ConfluenceRpcInterface interface. We have already discussed about dropping xmlrpc dynamic proxies in favor of swizzle and the advantages this brings. This would be the last step towards dropping dynamic proxies, and would ensure that there is no confusion for users (of course this will also be documented on xwiki.org). 2) Remove the domain objects in the xwiki xmlrpc package. Again, we are already using the swizzle domain objects. The only thing we still have to settle is whether we will do it directly or through a facade, and whether this facade will be part of xwiki or part of swizzle, but this is the subject of another discussion. 3) Remove XWikiRpcHandler and XWikiRpcInterface. They are an attempt to implement the JSPWiki interface that was not put into practice so far. Currently only 2 methods are implemented: getPage and getAllPages which return a string and a list of strings respectively. Even if fully implemented I don't think that the JSPWiki interface would be useful, since we already have the confluence api which is much more powerful. The other xwiki modules will probably not be affected by these changes. Existing users of the removed classes and interfaces will have to adapt their code. However, since we just went from an "almost working" implementation of XML-RPC to a working one, I believe that this is the best moment to clean things up and make everything more maintainable for the future. WDYT? Regards, Catalin