Yes, that is quite puzzling. I'm using the latest version, 3.1.3, though I'm away from the pc right now so I'll have to absolutely confirm later. How do people generally deal with this reverse problem? That might get me looking in the right place.
Jochen Wiedmann wrote: > > Which version are you using? This is quite puzzling, because people > are usually having problems because the XML-RPC client by default > omits the <string> tags? > > Jochen > > > > On Thu, Jul 22, 2010 at 1:37 AM, Micky1 <hill...@hotmail.com> wrote: >> >> Hi all, >> >> I'm writing a client which communicates via XML-RPC to an embedded >> hardware >> server that supports it. My client.execute requests are failing because >> AXML-RPC wraps each parameter in type tags, whereas it appears that the >> server is expecting bare values. >> >> Just to make sure I'm clear, I'm currently sending requests including >> something like this (asterisks are to prevent the forum from interpreting >> the tags): >> >> <*param> >> <value> >> <string> >> foo >> </string> >> </value> >> </*param> >> >> Whereas the server is expecting: >> >> <*param> >> <value> >> foo >> </value> >> </*param> >> >> I suspect that I should be accessing the StringSerializer.STRING_TAG >> field >> and changing it to an empty string or perhaps null, but I'd appreciate >> some >> input. Custom ContentHandler? Point me in the right direction. >> >> Thanks, >> Mick >> -- >> View this message in context: >> http://old.nabble.com/Customizing-XML-markup-tp29231900p29231900.html >> Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com. >> >> > > > > -- > Germanys national anthem is the most boring in the world - how telling! > > -- View this message in context: http://old.nabble.com/Customizing-XML-markup-tp29231900p29238182.html Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com.
