I have had a Ruby xmlrpc/server instance running for awhile now. Using
both Ruby and Python xmlrpc client apps I have been able to
successfully pass information back and forth. Trying a Dolphin
Smalltalk xmlrpc client app I had to tweak their implemention a bit
since it wasn’t passing ‘Content-Type: text/xml’ in the HTTP header and
apparently the Ruby xmlrpc/server instance requires this to be set.
After doing so the Dolphin Smalltalk xmlrpc client worked as well.
But now I am having issues getting a SuperWaba xmlrpc client to receive
the information back from the Ruby xmlrpc/server instance. This
implementation is based on Apache’s xmlrpc 1.0 library so it should be
pretty standard. Is there something that’s incompatible that anyone is
aware of? I can see the xmlrpc calls being received on the Ruby
xmlrpc/server end, and can see a result set/code being passed back out
to the xmlrpc client. But that’s where it ends. The SuperWaba xmlrpc
client reports back an unexpected response from the server with a null
I know that this might be more of a client issue than a server one, but
has anyone run into problems getting the Ruby xmlrpc/server
communicating with other types of clients?