Thanks Jochen, now i atleast know that its not the code that i wrote was faulty; I am now gonna start looking into "custom data type" its a big task for me since i am not really gud at understanding by looking at the javadocs;
Jochen Wiedmann wrote: > > On Wed, Mar 12, 2008 at 10:56 AM, fahad.aizaz <[EMAIL PROTECTED]> > wrote: > >> >> <member><name>originNodeType</name><value><string>TEST</string></value></member> > > [...] > >> <member><name>originNodeType</name><value>TEST</value></member> > > [...] > >> The tag <string></string> is missing from the output xml data above. > > The XML-RPC spec specifies the absence of any type indicator as > equivalent with the use of the "string" indicator. In other words, it > is the servers fault that it doesn't accept your response. > > However, to know that won't help you. Visit > http://ws.apache.org/xmlrpc/advanced.html and find the section on > "Custom data types". What you need is to have a custom type factory > with a custom TypeSerializer for the String class. The default > TypeSerializer for string is omitting the <string> tag, your's would > add it. > > > Jochen > > > > -- > Look, that's why there's rules, understand? So that you think before > you break 'em. > > -- (Terry Pratchett, Thief of Time) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/embedding-a-string-into-structure-XML-RPC-request-tp16001079p16004677.html Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
