XMLRPC serialization bug?

A

Andrew Knott

serializes the name / value parts of a struct in the wrong order?

If I do a calll as below

templatevalues = [:name=>"code",:value=>"thecode"},{:name=>"name",
:value=>"the name" }]

result =
server.call("OrangeAPI.SendSmsTemplate",{:username=>"",:password=>"",:"remote-ip"=>""},
{
:templateValues => templatevalues
})


BUG?: it always produces after serialization - with the value first,
rather than the name


<member><name>templateValues</name>
<value>
<array>
<data>
<value>
<struct>
<member>
<name>value</name>
<value><string>the code</string></value>
</member>

<member>
<name>name</name>
<value><string>code</string></value>
</member>
</struct>
</value>

<value>
<struct>
<member>
<name>value</name>
<value><string>the name</string></value>
</member>
<member>
<name>name</name>
<value><string>name</string></value>
</member>
</struct>
</value>
</data>
</array>
</value>
</member>



I know you're not supposed to assume any order in XML but is there any
way around this?

Andrew
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,755
Messages
2,569,537
Members
45,022
Latest member
MaybelleMa

Latest Threads

Top