I wanted some clarification regarding SudzC for iPhone. Does SudzC support SOAP 1.2?
I tried using SudzC with the web service http://www.restfulwebservices.net/wcf/CurrencyService.svc?wsdl and it works fine but with my web service it doesn't. The only difference I can spot is that the above service uses SOAP1.1 while mine used 1.2.
Regards,
EC
You pretty much answered your own question. A service expecting a soap 1.2 message is not required to be backward compatible to soap 1.1 formatted messages. You can configure WCF to accept soap 1.1 messages by creating a custom binding as show here. Although that WCF config is for a client, you can also configure a service to use that custom binding. If the service needs to support soap 1.2 messages, you can just leave your existing endpoint configured as-is and create a new endpoint for the soap 1.1 custom binding.
Related
I'm trying to proxy an SOAP EPR using API Manager.
I follow the procedure of creation of REST API "I have a SOAP End Point" and I provide the WSDL. but in the "design" tab i can't see the methods. Seems like API Manager "does not understand" the WSDL I provided.
I can browse The same WSDL and I used SOAPUI client, the WSDL is correct and I can see the methods and test them.
Does anyone exerienced this kind of issues with API Manager?
Best regards.
Before APIM 2.2.0 you will see only a single resource.
Enhanced support for exposing SOAP services as REST APIs by auto-generating the REST interface by parsing the WSDL of the SOAP Service was introduced in APIM 2.2.0.
When you have soap webservice, you can always use soapui to create test xml requests for manual interface tests. You insert you test data into the xml document and send the request to the soap provider. You can then analyse the response in soapui.
We are currently thinking about switching from soap with xml to grpc with protobuf3. Is there a test gui for grpc that offers features as described above for grpc?
I don't think the equivalent tooling is readily available, but we do continuously try to improve the state of tooling for gRPC and Protocol Buffers.
In the meantime, there is grpc_cli project that might be immediately helpful, and gives you an idea if you want to build your own similar tool.
You could use https://kreya.app, which is a gRPC GUI client, very similar to SoapUI for SOAP services (or Postman for REST services).
Disclaimer: I'm one of the authors of Kreya.
I create a client in Domino to consume a web service that works with SOAP 1.2 and has HTTPBinding.
The client generation tool for Domino Designer Web services an error is displayed when trying to generate reporting that the SOAP accepted version is 1.1.
I decided to create the client with CXF framework through tool wsdl2java. In an agent I used these classes to consume the web service, however the below error was displayed. I think it's because of the SOAP version, but I'm not sure.
com.sun.xml.internal.ws.protocol.soap.MUTube getMisUnderstoodHeaders
INFO: Element not understood={http://www.w3.org/2005/08/addressing}Action
Also generated a jar of classes generated by wsdltojava and imported to another agent, but the error below is displayed.
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=, offset=6
The question is, no way consume a web service with SOAP 1.2 in Domino only supports up to version 1.1?
Thanks a lot!
I don't believe that Domino's web service consumer supports SOAP 1.2 at this time. You might be able to do what you need with an agent though - here's one way: How can I call a SOAP 1.2 Web service from a LotusScript agent?
In fact there is no way to natively consume a web service with soap version 1.2. There are already several requests from IBM to upgrade the SOAP version. What I did, was to develop a new layer through a new web service with the version SOAP 1.1, which internally calls the web service with the SOAP version 1.2;
Is there any way to test rest Webservices in SAP?
I know it's possible to test SOAP Webservices with eCATT but to do that a WSDL file is needed.
The Problem with rest Webservices is, there is no such WSDL file.
Thanks in advance.
I'm assuming from your question that you'd like to test the service from within your SAP system rather than by using an external tool.
If you have access to a system that has the Gateway components deployed, you can use the Gateway client (transaction code /IWFND/GW_CLIENT). It provides a very similar set of functionality to Postman, Paw, et al.
You can use some rest clients available on the browsers:
Postman -> Chrome
RESTClient -> Firefox
Futhermore, if you need a more robust client, you can use SoapUI. See this link.
You may use Fiddler.
Here is detailed instructions on how to test a web service (I know the instructions are for asp.net web services but the Fiddler part should work for any web services).
I went through http://cxf.apache.org/docs/jax-rs-client-api.html documentation but I am still not sure which type of rest client should be used in what use cases?
Can anyone point out the use cases / constraints with examples that would help me in choosing the right client API.
CXF 3.0 implement the JAXRS 2.0 client API, it makes your code can work with other JAXRS implementation without changing anything.
But if you are still using CXF 2.x, you need to chose between the Proxy Based API and WebClient API.
The Proxy Based API is much like the CXF JAXWS Client API, you can just invoke the service from a Proxy which implement the interface of SEI. It has some shortcomings, you cannot specify the http hears or write a generic client to invoke the different JAXRS services.
With the help of CXF WebClient API, you can invoke the JAXRS services in a normal HTTP client way, which just fill the gap of Proxy Based API.
You can find more information about those clients API here.