Great! Here it is: <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> <soapenv:Header/> <soapenv:Body> <ns1:replicate xmlns:ns1="http://ws.apache.org/axis2/services/replicate";> <qid>qid1</qid> <hostname>hostname1</hostname> <repl_id>d6ge5gyrgj4</repl_id> </ns1:replicate> </soapenv:Body> </soapenv:Envelope>
In the curl REST simulations show below I used names aa, bb, dd to highlight how the names caused the order of the nodes to become alphabetically sorted within the server, causing node traversal to be an unreliable method of parsing. Brian On Jan 15, 2008 3:50 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > Please send the working SOAP request so that we can understand what the > payload should be. > > Samisa... > > > Brian McQueen wrote: > > I must be doing something wrong because I am seeing some odd handling > > of REST requests by the server. When I send in REST requests, the > > server does not seem to use the names of the parameters to identify > > them, but instead uses their order, or even imposes its own order by > > sorting them alphabetically? Its odd: > > > > curl > > http://localhost:9090/axis2/services/replicate/replicate\?aa=parm1\&cc=parm2\&dd=parm3 > > > > This parses into the expected order, but if I do (changing the name of > > the second parameter so its alphabetically last): > > > > curl > > http://localhost:9090/axis2/services/replicate/replicate\?aa=parm1\&ee=parm2\&dd=parm3 > > > > then the parsed order of the parameters is parm1, parm3, parm2. > > > > How am I supposed to be parsing these REST requests? I have code the > > parses the SOAP fine, but I started testing it on REST today and found > > this odd behaviour. > > > > Brian McQueen > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
