As noted, i have the host and server... but how does one make a wsdl request over tcp?
That is, i want to see the returned wsdl file!
This is the format to get the wsdl file from the server
http://url:port/WebServicesName?wsdl
Related
I searched for an answer and I could only find this: Generate WSDL for existing SOAP Service using captured traffic, however it links to online tools that no longer exist.
I have this SOAP request: https://justpaste.it/ddajc
And this SOAP response: https://justpaste.it/aug1m
How do I create the WSDL?
I have SOAPUI running mock REST and returing some json resonse, this part is working okay.
On the SoapUI server, I would like to save the binary file attachment from the client's REST request, which is coming from another client application not SOAPUI test request, to SOAPUI server side during processing of the client's request. Where do I start with this?
Thanks
I have a web server that handles configuration set-up for various IO devices. I need to get some data from a REST server that is running on a different server. Can that web server code issue a client REST GET command to a REST server running on a different server? I tried it but I get a http 500 error. The server code is failing on the REST server request code.
I am closing out this question. Yes, your server can issue http requests to other services. I was having another problem with a self-signed certificate and the error made it look like their was a problem with my http request service.
I was recently working quite a lot on SOAP web services and one question bothers me in that context. What would be better?
A. Get the WSDL and store it locally on client side and then only make calls to the service
if server keeps backward compatibility the client will still work with the old WSDL even when server side provided new version (of service and WSDL).
you are not able to get endpoint URL from WSDL so if service endpoint location has changed (but WSDL not) you need to reconfigure the client.
no additional call to the server
B. Use WSDL location as remote resource (HTTP) and download WSDL each time client instance is created?
What are some pros and cons?
Which is better depends on your setup and your needs but personally I would prefer having the WSDL locally, inside the client for these reasons:
no extra call to the server to get the WSDL (as you mentioned);
if server keeps backward compatibility the local WSDL will still be OK to use (as you mentioned);
if the service WSDL changes in an incompatible way and your client suddenly starts to fail you still have the old WSDL locally and you can compare it with the new one to see what's different.
The following point is usually not an issue:
you are not able to get endpoint URL from WSDL so if service endpoint location has changed (but WSDL not) you need to reconfigure the client.
The endpoint URL in the WSDL is not always correct and even if it was, you normally have the WSDL accessible at the same URL as the service by just sticking a ?wsdl parameter after it so if the location changes you won't find the service but you wont find the WSDL either. The service endpoint URL needs to be configurable in your client anyways.
My remote server expose some methods in WSDL. Is it possible to use this WSDL within jasper server to get data? I looked into examples that Jasper consume data that are available in the XML but didn't found anything on using web service (WSDL).
Thanks