> Hi all,
>
> In the old helma code this was handled by returning null, which is
> not in the xmlrpc spec. We had to change all of our void methods to
> return boolean. It was a bit of work, but worth it.
>
Yep - reading the spec I came to the conclusion that neither "void" nor "null"
were really legal return types. So even if we hacked our handler here, it would
cause problems for other handler implementations.
Route we took was to always return a Hashtable which contained one or both of
2 keys:
"wrapped-return" - boolean key indicating this is a wrapper
"return-value" - present if above key is present, and non-null or non-void
return
Our client side interface proxy code checks for a Hashtable, and if it contains the
"wrapped-return" key it unwraps any "return-value" (giving null if void or non-
present).
Any Hashtable not containing the "wrapped-return" key is just passed back to the
caller.
-- Rob
SoftSell Business Systems, Ltd.
' testing solutions for a changing world '
+44 (20) 7488 3470
www.softsell.com
[EMAIL PROTECTED]
