How to work with this kind of server
http://136.243.3.6:8888/wsLoyalty/Loyalty.1cws?wsdl
I mean how to response, request and so on
You need to create a soap envelope to send request and will need to use XML parsing to read response
Refer this
Related
I want to send below as a form-data in API Body for a PUT request:
Upload a file(KEY) with "Error.png"(VALUE)
Send text, "MyName"(KEY) with false(VALUE)
How to do this using REST-Assured
I don't seem to understand the question completely, but if you're trying to upload a file then you can use
given().multiPart("file2", new File("/home/test/some_large_file.bin"))
If you wish to send the file as as a RAW data you can use Tool to encode the file and send the value in the payload
I'm trying to use RestClient and Faraday to query an endpoint which returns multiple files in a multipart response. How do I parse the multipart envelopes in the response body? Rack::Utils::Multipart.parse_multipart would have done it, but in my case, this is outside of Rack. I'm open to using a different HTTP client if its helps.
Almost none of the popular HTTP clients, in almost any language, handle multipart responses from a server. In fact I'd be surprised if you can easily find HTTP servers with baked in multipart response capabilities. It's just not a common use case.
You'll find the converse true though, most HTTP servers handle multipart responses built from clients.
The good news is that "multipart" is just content type like XML or JSON, so you should be able to attach any old multipart parser to the response body after you've made the request with your favorite HTTP client.
Some parsers to consider:
https://github.com/danabr/multipart-parser
Rack::Multipart::Parser
Shoehorn your data into Rack::Utils.parse_multipart
Is there a way to get the response of SQS Api as Json?
I need to do it because from the browser I need to get the information of the queue, but as it is cross-domain it needs to be in json(p)
#see Receive XML response from Cross-Domain Ajax request with jQuery
SQS does not provide a JSON interface. You could implement a proxy on your web server which returns the information in whatever format you want. That would also remove the cross-domain issue.
Can ASIHttpRequest call Restful web service ? I knew that Restkit is good at it.
If no,any easy way to convert ?
Can we say that ASIHttpRequest is good at calling soap based web service ?
Thanks for your comments !
ASIHTTPRequest simply does a HTTP request. Nothing more, nothing less. Since REST is also just an HTTP request, you can use ASIHTTPRequest just fine with a restful web service. It doesn't do any parsing of the response, though, so if the response is JSON you still have to parse that yourself.
You can also use ASIHTTPRequest for SOAP but you have to construct the XML by yourself (or using some other library) and parse the XML response by yourself as well. For SOAP you may want to use http://sudzc.com/ instead.
Is there a recommended way / a tutorial which shows how to create and process plain SOAP request with Delphi without THTTPRio, for example, if I want to implement SOAP over JMS, SOAP over AMQP or SOAP over SMTP?
Simplified code examples:
// create a SOAP request (client side)
RequestXML := Service.Add(Arg1, Arg2);
This code would generate the XML with the SOAP message for the 'Add' method invocation with the arguments Arg1 and Arg2.
// process a SOAP request (server side)
ResponseXML := Service.ProcessRequest(RequestXML);
This code would take the SOAP request XML and invoke the method. The result of the method invocation will be wrapped as a SOAP response and is ready to be sent to the client.
Take a peek at the TLinkedRIO class ( http://shenoyatwork.blogspot.com/2004/10/using-tlinkedrio.html ). It creates the SOAP request and writes it to a file. Since TLinkedRIO is used for testing purposes, it also contains code to find a (Delphi) Server that implements the Service and have the server read the request from the file, process it and write a response to another file. The caller (client) then reads from the response file. If you want to use a different transport you won't have to do that part: the response will come from a true Service. However, it's a good example to show how the XML serialization is separate from the transport.
PS: The SOAP serialization basically expects IWebNode for its transport needs. And namely the Execute method of that interface. How/where you send the request stream to and how/where you get the response stream from is up to the transport implementation.