[issue8792] xmlrpclib compatibility issues with Apache XML-RPC library

Martin v. Löwis added the comment: Can somebody please point to a current version of the Apache documentation? The link in msg106322 does not work anymore. I'm tempted to close this as invalid: Apache is clearly violating the XML-RPC specification, so the bug is theirs. As a work-around, add

[issue8792] xmlrpclib compatibility issues with Apache XML-RPC library

Bhargav added the comment: I am seeing the same exception when the server returns ex:nil, even when I enable allow_none. The library only accepts 'nil' not 'ex:nil' As a workaround, I have added dispatch["ex:nil"] to my local library (which is obviously not a solution) -- nosy: +bha

[issue8792] xmlrpclib compatibility issues with Apache XML-RPC library

Brian Quinlan added the comment: A few notes: 1. these types are *not* part of the XML-RPC specification, they are Apache extensions 2. these types seem designed to accommodate Java 3. some of these types would be very possible to accommodate e.g. ex:serializable which contains a serialized Ja

[issue8792] xmlrpclib compatibility issues with Apache XML-RPC library

Changes by Antoine Pitrou : -- nosy: +loewis versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue8792] xmlrpclib compatibility issues with Apache XML-RPC library

New submission from Attila Nagy : When talking to an Apache XML-RPC library based application via python 2.6.5 xmlrpclib, I get this exception: Traceback (most recent call last): File "prb.py", line 4, in proxy.catv.getEndpointIdByIp('1.1.1.1') File "/tmp/Python-2.6.5/Lib/xmlrpclib.py",