Hi, general remark: if you really want to see what is transmitted between client and server, you can always use eg. wireshark to capture the TCP stream.
But more concrete: your two solutions are totally different: 1) plain java. you just copy your xml to the socket. And your XML is not valid XML RPC request (see http://www.xmlrpc.com/spec ) for an example. 2) using xml rpc. your xml now goes only as String (I guess that get("xml") returns String) parameter of the XML RPC call auth, ie. there is some XML RPC stuff and inside is your XML as string parameter of XML RPC call (see spec once again) I hope I help little bit and I was not confusing ;-) Regards Stano On Wed, Mar 4, 2009 at 09:49, lplpp <latikap...@gmail.com> wrote: > > Also the xml that IO ma sending as a string is as below: > > ======================================== > <Request timestamp="20010403123245" type="auth"> > <merchantid>aisling</merchantid> > <account>internet</account> > <orderid>ord-123</orderid> > <amount currency="EUR">2000</amount> > <card> > <number>490303400005718902</number> > <expdate>0403</expdate> > <chname>John Doe</chname> > <type>MC</type> > <issueno></issueno> > <cvn> > <number>453</number> > <presind>1</presind> > </cvn> > </card> > <autosettle flag="1"/> > <md5hash>2bf9800c5170836d9cc76d67079f24bd</md5hash> > </Request> > -- > View this message in context: > http://www.nabble.com/XMLRPC-giving-issues-while-sending-the-entire-xml-as-string-parameter-tp22325716p22325928.html > Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com. > >
