At 02:44 PM 11/20/01 -0600, Ian Bicking wrote: >On Tue, 2001-11-20 at 14:16, Geoff Talvola wrote: > > First, make sure that the Application.config setting > > IncludeTracebackInXMLRPCFault is set to 1. I think it is set to 1 by > > default, but I'm not positive. What this means is that if your XML-RPC > > method raises an exception, the text of the traceback will be returned to > > the client in an xmlrpclib.Fault object in the faultString > > attribute. Here's an example using the XMLRPCExample servlet included > with > > Webware: > >Yes, IncludeTracebackInXMLRPCFault does default to 1. > >I'm afraid I'm getting a ProtocolError instead of a Fault. I was >getting the same behavior, I believe, when I was sending unsupported >types (some binary data and None). I don't *think* I'm sending >unsupported data this time, but it's hard to tell. > >I'm using xmlrpclib 0.9.8 -- I think there's a beta version, but I don't >know if it improves handling of this sort of error.
It's easy to poke around in XMLRPCServlet.py and add additional logging that would be useful. For example, you can have it log the incoming and outgoing XML packages by adding "print data" and "print response" at the appropriate places. Maybe that will help... -- - Geoff Talvola [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
