[ http://issues.apache.org/jira/browse/XMLRPC-18?page=all ] Jochen Wiedmann closed XMLRPC-18: ---------------------------------
Resolution: Won't Fix Assign To: (was: rpc-dev mailing list) I am honestly respecting Martin's work. Nevertheless, this is still incomplete, after almost four years. I am closing this now. For version 3, I really suggest to use an SSL implementation like java.net or org.apache.httpclient on the client side and a serious servlet engine like Tomcat or Jetty on the server side, > Secure functionality is poorly documented, and difficult to get working. > ------------------------------------------------------------------------ > > Key: XMLRPC-18 > URL: http://issues.apache.org/jira/browse/XMLRPC-18 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: Other > Platform: All > Reporter: Martin Redington > Attachments: SECURE_README.txt, TestSecureClient.java, > TestSecureServer.java, list_archive_info.txt, original_post.txt > > Secure functionality (e.g. using the SecureWebServer and SecureXMLRPCClient > classes is poorly documented, and very difficult for a naive user to get to > work correctly. > The non-obviousness of the correct approach is illustrated by the failure of > queries to rpc-users on how to get the attached sample code to work to > generate any response. -- 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