From: Matt W. <ma...@en...> - 2007-03-11 02:14:29
|
Hello All, I have spent the last 6 hours looking for a solution to this issue, but I seem to be going around in circles. I started by following the perl example as set out on the developer documentation for a simple 'execute', using a 'string' type for the query, which threw up the following: java.lang.NoSuchMethodException: org.exist.xmlrpc.RpcAPI.execute (org.exist.security.User, java.lang.String) After reading a mail in the archive it appears that strings are now to be passed as base64 in order to overcome unicode issues - so I can understand why I would obtain the result above. After converting the query to a 'base64' type, and attempting the query via XML-RPC I get the following faultString: java.lang.NoSuchMethodException: org.exist.xmlrpc.RpcAPI.execute (org.exist.security.User, [B) The request I am sending to the eXist server is: <?xml version="1.0" encoding="UTF-8"?> <methodCall> <methodName>execute</methodName> <params> <param> <value> <base64>Zm9yICRzcGVlY2ggaW4gLy9TUEVFQ0hbTElORSAmPSAndGVhcionXQpvcmRlciBi eSAkc3Bl ZWNoL1NQRUFLRVJbMV0KcmV0dXJuCiAgICAkc3BlZWNo </base64> </value> </param> </params> </methodCall> Which I would have thought to be correct. The same occurs for the other methods I have tried. The query itself is the same as used in the developer documentation, and works in the sandbox on my local machine. I have tried with both 1.0.2-rev5396 and 1.1.1-newcore with equal effect. Can anyone shed any light on this for me? Kind Regards, Matt Williams ------------------------------------------- Matt Williams Energy Mind Limited ma...@en... Web: www.energymind.com Tel: 0845 004 6382 Mob: 07958 208482 This electronic mail transmission from Energy Mind Ltd is intended for the named recipients only. It may contain private and confidential information. If this has come to you in error you must take no action based upon it, nor must you copy it or show it to anyone; please telephone us immediately and return the original to us. We cannot accept any liability for any loss or damage sustained as a result of software viruses. It is your responsibility to carry out such virus checking as is necessary before opening any attachment which may be included with this message. |