[ http://issues.apache.org/jira/browse/XMLRPC-28?page=comments#action_12331713 ]
Steve Cohen commented on XMLRPC-28: ----------------------------------- No kidding! I spent several hours how to embed XMLRPC in a servlet. I couldn't get anywhere until I figured out that the comment on this page: http://ws.apache.org/xmlrpc/server.html "Note that the XML-RPC client in Frontier 5 has its requests hard-coded to URI /RPC2. To work with these clients, you have to configure your server environment to respond to /RPC2. This should be fixed in a newer version." actually applied to the entire package and not just to Frontier 5 (whatever that is). Changing my servlet mapping to /RPC2 made it all work. Also on this page was: "A full example servlet is included in the package. There is a sample XML-RPC Servlet included in the library. You can use it as a starting point for your own needs." I wouldn't say that was exactly true. There was, to be sure XmlRpcProxyServlet, but there are many things about that sample such as the purpose of the URL configuration parameter that weren't explained and contributed to my confusion. (again, only /RPC2 seemed to work). Was this the example servlet you had in mind? It would be good if the page gave the name of this aid. Anyway, after getting over these initial humps, the package did appear quite straightforward to use. However, in looking over these issues, it seems that there are issues almost two years old that are not resovled. Is this project being actively maintained? That would be a factor in whether or not my organization decides to use it. Thank you. Steve Cohen > Client usage documentation is out of date > ----------------------------------------- > > Key: XMLRPC-28 > URL: http://issues.apache.org/jira/browse/XMLRPC-28 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Ryan Hoegg > Assignee: Ryan Hoegg > > xdocs/clients.xml describes an outdated method for using the client. Of > course, > the new API is still settling down a bit; however, I am beginning to think if > we > document it first it may help focus our efforts. > I would have just updated it but until I get around to it we may as well have > something indicating it needs to be done. -- 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
