[ http://issues.apache.org/jira/browse/XMLRPC-75?page=comments#action_12367476 ]
Jochen Wiedmann commented on XMLRPC-75: --------------------------------------- Walter, are you interested in getting this into the 3.0 branch? If so, let's do it in a few steps. - First of all, you should propose necessary extensions for the interfaces handlermapping and handler. (Recommended: Create an interface like XmlRpcMetaDataHandlerMapping, which extends XmlRpcHandlerMapping.) - Second: Make the existing classes implement your new interfaces. - Third: Provide special handlers, which provide the requested metadata. > Introspection Patch for XML-RPC, current to SVN 2005-12-29 (r359943) > -------------------------------------------------------------------- > > Key: XMLRPC-75 > URL: http://issues.apache.org/jira/browse/XMLRPC-75 > Project: XML-RPC > Type: New Feature > Components: Source > Versions: unspecified > Reporter: Walter Mundt > Attachments: IntrospectionExample.java, xmlrpc-2.0-beta-introspection.patch > > I've taken Aaron Hamid's Introspection patch (which was in turn derived from > the one here: > http://xmlrpc-c.sourceforge.net/hacks/helma-xmlrpc-introspection.diff ) and > basically rewritten it to work with the current XML-RPC library. > I tried to set it up so that it followed the existing coding style as much as > possible, and would not break any existing applications. For example, when I > needed a list of handlers supported by a particular mapping, I added a new > interface XmlRpcListableHandlerMapping that provides this information, made > the default handler implement it, and designed my code so that if it were not > implemented by a handler in use, everything would work except the > system.listMethods functionality that relies on it. > I hope you will be able to integrate this code into the next version of the > library; please contact me with any questions or issues. I will be attaching > the patch to this issue if I can so that the problem with his previous patch > will not occur. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
