Hi All,
Using 1.5.2 (just downloaded) the issue is still not fixed.
I am still getting in my XML-RPC Server log:
<methodCall>
<methodName>system.methodSignature</methodName>
<params>
<param>
<value>
<string>columbusom.Enterprise</string>
</value>
</param>
</params>
</methodCall>
Run the exact transaction using 1.5.0 I get:
<methodCall>
<methodName>columbusom.Enterprise</methodName>
<params>
<param>
<value>
<string>localhost:IOP:8082</string>
</value>
</param>
<param>
<value>
<string>rwc</string>
</value>
</param>
</params>
</methodCall>
My comment on the issue tracker asks if this is going to be fixed for 1.5.3.
Testing against the Incutio server the result with 1.5.2 is still
problematic using the following example code.
$conn = new
Zend_XmlRpc_Client('http://scripts.incutio.com/xmlrpc/simpleserver.php');
try {
$result = $conn->call('test.getTime');
echo $result, "\n\n";
} catch (Zend_XmlRpc_Exception $e) {
echo $e->getMessage() . "\n\n";
}
echo $conn->getLastRequest()->__toString();
The result is:
server error. requested method system.methodSignature does not exist.
<?xml version="1.0" encoding="UTF-8"?>
<methodCall><methodName>system.methodSignature</methodName><params><param><v
alue><string>test.getTime</string></value></param></params></methodCall>
Using 1.5.0 gives you:
22:17:35
<?xml version="1.0" encoding="UTF-8"?>
<methodCall><methodName>test.getTime</methodName></methodCall>
-----Original Message-----
From: Jake McGraw [mailto:[EMAIL PROTECTED]
Sent: 09 July 2008 19:40
To: fw-general@lists.zend.com
Subject: Re: [fw-general] XML RPC calls no longer working in 1.5, possibly
due to server introspection?
> Is this still the case for the 1.5.2 release or current trunk? The
> indications on that bug are that it's fixed.
>
Looking at 1.5.2, looks like this was fixed.
- jake
>
>> <?php
>> /**
>> * FIXME Use this class instead of Zend_XmlRpc_Client until bug is
>> fixed
>> * http://framework.zend.com/issues/browse/ZF-2978
>> */
>> class BugFixXmlRpcClient extends Zend_XmlRpc_Client {
>> public function call($method, $params = array())
>> {
>> $request = new Zend_XmlRpc_Request($method, $params);
>> $this->doRequest($request);
>> if ($this->getLastResponse()->isFault()) {
>> $fault = $this->getLastResponse()->getFault();
>> throw new
>> Zend_XmlRpc_Client_FaultException($fault->getMessage(),
>> $fault->getCode());
>> }
>> return $this->getLastResponse()->getReturnValue();
>> }
>> }
>>
>>
>> - jake
>>
>>
>> On Wed, Jul 9, 2008 at 11:52 AM, David Edwards
>> <[EMAIL PROTECTED]> wrote:
>> >
>> > Hi,
>> >
>> > We have been using the ZF XmlRpc classes to communicate with our
>> > payment gateway for a while now, and this has worked fine for us in
>> > the past (using 1.0.x). However, in testing a newer version of the
>> > ZF libraries (1.5.x), our XML RPC calls stopped working, giving out the
error:
>> >
>> > java.lang.Exception: RPC handler object "system" not found and no
>> > default handler registered
>> >
>> > Having dug around a bit, it appears that Zend_XmlRpc_Client now
>> > includes some code to handle empty array parameters in the call()
>> > method (according to the comments in the code), and it's in this
>> > block that the client makes an additional method call
>> > (system.methodSignature), to which the gateway server replies with the
above error.
>> >
>> > I'm a bit stuck as to what's happening here. Is it the case that
>> > the payment gateway is breaking the XMLRPC spec (i.e. there should
>> > be a system object on the other end)? Is there a way to get
>> > Zend_XmlRpc_Client not to perform these calls? Any advice on the matter
is greatly appreciated.
>> >
>> > Many thanks,
>> >
>> > David Edwards
>> > --
>> > View this message in context:
>> > http://www.nabble.com/XML-RPC-calls-no-longer-working-in-1.5%2C-pos
>> > sibly-due-to-server-introspection--tp18363733p18363733.html
>> > Sent from the Zend Framework mailing list archive at Nabble.com.
>> >
>> >
>>
>
> --
> Matthew Weier O'Phinney
> Software Architect | [EMAIL PROTECTED]
> Zend Framework | http://framework.zend.com/
>
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
