ID:               38429
 Updated by:       [EMAIL PROTECTED]
 Reported By:      giunta dot gaetano at sea-aeroportimilano dot it
 Status:           Open
-Bug Type:         XMLRPC-EPI related
+Bug Type:         Feature/Change Request
 Operating System: windows 2000
 PHP Version:      5.1.4
 New Comment:

Reclassified as feature request.


Previous Comments:
------------------------------------------------------------------------

[2006-08-11 13:31:19] giunta dot gaetano at sea-aeroportimilano dot it

Description:
------------
When registering a php user function to be exposed as xmlrpc method,
the resulting xml will be that of an xmlrpc fault response iff the
return value of the user function is an array containing a key
'faultCode'.

When the result value contains other array members beside faultCode and
faultString, or the values of those two members are not an int and a
string, the generated xml will not be conforming to the xmlrpc spec,
which states: "A <fault> struct may not contain members other than
those specified".

I know that this situation is the fault of the coder, but, imho, the
lib should do its reasonable best to always work within the spec...


Reproduce code:
---------------
$x = xmlrpc_server_create();
xmlrpc_server_register_method($x, 'pluto', 'pippo');
$out = xmlrpc_server_call_method($x, xmlrpc_encode_request('pluto',
array()), null);
echo htmlspecialchars($out);

function pippo($meth, $params, $extras)
{
return array('faultCode' => 1, 'faultString' => array(1, 2, 3, 4),
'hello world');
}

Actual result:
--------------
<?xml version="1.0" encoding="iso-8859-1"?> <methodResponse> <params>
<value> <struct> <member> <name>faultCode</name> <value> <int>1</int>
</value> </member> <member> <name>faultString</name> <value> <array>
<data> <value> <int>1</int> </value> <value> <int>2</int> </value>
<value> <int>3</int> </value> <value> <int>4</int> </value> </data>
</array> </value> </member> <member> <name/> <value> <string>hello
world</string> </value> </member> </struct> </value> </params>
</methodResponse>


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=38429&edit=1

Reply via email to