Okay, I figured out what I was doing wrong. Client says List, server
says (int, String, etc).
Thanks,
Steve
-----Original Message-----
From: Lewis, Steven (MED US)
Sent: Monday, February 12, 2007 4:49 PM
To: xmlrpc-dev@ws.apache.org
Subject: Trying List: No method matching arguments
Hey guys,
First, let me say that we've been using XMLRPC 2.0 in production and
have found it very satisfactory. We have python calling an xmlrpc2.0
servlet, primarily using reads.
Now we're looking into using xmlrpc 3.0, sending parameters in (instead
of just empty param list). I'm having a little trouble. The server
method looks like this:
public int testList(List list)
{
return 1;
}
The client code looks like this:
List list = new ArrayList();
client.execute("test.testList", list);
I'm getting the "No method matching arguments" response from the xmlrpc
servlet. (I also see a similar error in my Tomcat logs).
Any ideas on what I'm doing wrong? I checked the FAQ and tried to google
an example for using lists, but nothing obvious came up. I really hate
to post to the dev list for something this simple. I do have a unit test
working of just sending in a single String parameter, so my setup seems
to be working at a basic level.
Thanks!
Steve
------------------------------------------------------------------------
----
This message and any included attachments are from Siemens Medical
Solutions
and are intended only for the addressee(s).
The information contained herein may include trade secrets or privileged
or
otherwise confidential information. Unauthorized review, forwarding,
printing,
copying, distributing, or using such information is strictly prohibited
and may
be unlawful. If you received this message in error, or have reason to
believe
you are not authorized to receive it, please promptly delete this
message and
notify the sender by e-mail with a copy to
[EMAIL PROTECTED]
Thank you
----------------------------------------------------------------------------
This message and any included attachments are from Siemens Medical Solutions
and are intended only for the addressee(s).
The information contained herein may include trade secrets or privileged or
otherwise confidential information. Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful. If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to [EMAIL PROTECTED]
Thank you
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
