@namita 1: you are again mixing two prtocols in your calls! This time jsonrpc and xmlrpc. Please take the time to understand what these 3 words mean: json-rpc, xml-rpc, soap. Read about them on wikipedia.
In short: the server is answering with a jsonrpc response to the client. This response contains an error message. The error message is: "the client sent a request that is not valid according to my protocol".
You should either
change the jsonrpc server into an xmlrpc server, or
in the payload you create in the debugger write some valid json data, not some xml data
@namita 2: if you want to create a webservice in eZP with the ggwebservices extension and consume it from a .net application, you currently have two choices:
use a library in your .net application that speaks the xml-rpc or json-rpc protocols and use that library for the client
wait a few weeks (possibly months) until there is good support for SOAP+WSDL servers within the extension. Currently only the SOAP+WSDL client is there, but I am working on the server implementation. I do not promise release dates, though.
Principal Consultant International Business
Member of the Community Project Board
Another solution is to forego completely eZP native SOAP support, and code you server from scratch using custom modules/views. Example code for the view: