[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-user
Subject:    RE: XmlRpcClient execute for vector of string parameters produces incorrect XML on the wire?
From:       "John Southerland" <john () southerland-consulting ! com>
Date:       2005-08-25 6:02:59
Message-ID: 20050825061011.EBCC210FB2B5 () asf ! osuosl ! org
[Download RAW message or body]

Sorry about that, I was drinking and may have dialed the wrong number.
I am dirinking now and may be typing the wrong words as well.
I will try to call you tomorrow :)

John Buren Southerland
Southerland Consulting
801.467.8090(office)
214.734.8099(cell)
john@southerland-consulting.com
-----Original Message-----
From: rich coco [mailto:racoco@starbak.com] 
Sent: Wednesday, August 24, 2005 10:15 PM
To: xmlrpc-user@ws.apache.org
Subject: Re: XmlRpcClient execute for vector of string parameters produces
incorrect XML on the wire?

i believe <string> is the default, as defined by the xmlpc protocol.any 
xmlrpc-compliant server will treat such data as 'string'.

David Oppenheimer wrote:

>Hi. When I do the following
>
>XmlRpcClient xmlrpc = new XmlRpcClient("...");
>Vector params = new Vector();
>params.add(new String("hello"));
>xmlrpc.execute("function_name", params);
>
>I notice that what goes out over the wire is
>
><param><value>hello</value></param>
>
>instead of
>
><param><value><string>hello</string></value></param>
>
>Note that if I replace "new String("hello"))" with "new Integer(5)" in
>the above, then I get the correct text on the wire, namely
>
><param><value><int>5</int></value></param>
>
>Does anyone know why the <string> tag is being dropped? This might
>work if you're using the Apache XMLRPC server, but I'm using a
>different server and it is rejecting this formatting since it is
>expecting a string argument.
>
>Thanks very much for any suggestions,
>David
>  
>

[prev in list] [next in list] [prev in thread] [next in thread]