I had exactly the same problem.
No, xmlrpc does not support this out of the box.
I have written some fairly compact reflection-based code to convert Java
beans and Java collections into simpler structures that XML-RPC can
handle. As a bonus, it converts longs, characters, nulls, floats, and
othe
I've recently had to interface with a system that will remain un-named here that was
generating XMLRPC responses that had null values for an integer field.
I figured setting reasonable defaults for integers, doubles, and booleans is probably
better than having the entire XMLRPC transaction blow
The current DateTool can only deal with one form of ISO 8601 dates - one that look
like "MMddThh:mm:ss". Any time zone information is discarded by the
SimpleDateFormat object due to the format string. Even worse, any other variant of
ISO 8601 will cause the entire XMLRPC transaction to fai