Does anybody know or have even a hist how to implement SOAP 1.1 to SOAP 1.2 proxy using WSO2ESB?
Any combination of any configuration options lead to:
SOAP 1.2 request get transformed to SOAP 1.1 request,
but response from SOAP 1.1 service doesn't get transformed to SOAP 1.2.
None on examples, documentation articles fits to my case. Looks like everybody think that it should work our of the box, but it doesn't.
Related
We are trying to perform tests using Rest Assured Api but we aren't getting success with the response. We sent a request but the response is a faultcode (xml). The same request was made successfully using Soapui.
So, we searched a lot, people say that rest assured supports SOAP and others says that doesn't support.
Anyone knows what is the truth? Supports or not?
While it does not specifically support SOAP protocol, nothing stops you from using RestAssured for SOAP Servers testing - because it is just sending and receiving XML over HTTP and RestAssured does this perfectly well.
To be honest, the fact that RestAssured is not specifically designed to support SOAP makes it even more valuable for error testing, which would be really difficult with SOAP-centered clients.
Here's more details how one can verify XML content: https://github.com/rest-assured/rest-assured/wiki/Usage#example-2---xml
Rest-Assured framework only supports testing REST services.
You can read the introductory post by Johan (Rest-Assured committer) in the below link:
https://www.jayway.com/2013/11/29/rest-assured-2-0-testing-your-rest-services-is-easier-than-ever/
Also in the source code of REST-Assured in Github, it is never mentioned about supporting SOAP services, or has code that supports it.
https://github.com/rest-assured/rest-assured
If you want a single framework supporting both REST and SOAP services try the following options.
http://www.citrusframework.org/
https://www.soapui.org/developers-corner/integrating-with-soapui.html
Currently, We are leveraging a REST API framework tool to automate large soap msgs for api testing, fundamentally rest and soap are same.
The only difference is SOAP msg payload is in xml and response is in xml, will have single header and single type of https request -POST.
you just have to write supporting utils for constructing payload and then processing response.
I created a REST service project in version 4.6.0, and added a mock. I'm not able to add an operation for the mock. I get..
No unique operations to mock in project!
I am able to directly modify the onRequest script and set the response status code for GET messages. However, when I switch to POST, which is what I really need, I get a SOAP fault string in the response:
org.apache.xmlbeans.XmlException: Missing/Invalid SOAP Envelope,
expecting [{http://schemas.xmlsoap.org/soap/envelope/}Envelope]
How can I bypass soapUI's SOAP processing of the message? I'm trying to post a plain old XML message, not SOAP.
posting: <test></test>
As Temil Sanchez writes for a question asked on the soapUI forum:
Rest Mocking was not that fully supported in 4.6.3, the only
workaround for Rest Mocking in 4.6.3 is located here :
http://www.soapui.org/Getting-Started/mock-services.html
rest mocking becomes much easier to do in our SoapUI 5.0 Release which
should be available on April 1st. In the meantime we have a Beta that
you can try here:
http://forum.soapui.org/viewtopic.php?f=2&t=23529
I'm using CXF 2.2.12 library for my Web Services.
Is it possible to use MTOM (Message Transmission Optimization Mechanism)
in RESTful response?
Would appreciate any links to docs/tutorials regarding this. Thanx!
MTOM is specific to SOAP so I would argue that it is incompatible with a RESTful architecture. However, HTTP supports multi-part content naturally, so you can do everything that MTOM does in HTTP directly.
If you really wanted you could use XOP for packaging your multi-part content like MTOM does, but it really isn't necessary.
MTOM is solving a problem that HTTP already solved.
The numerous technologies for writing SOAP web services allow me to create services which adhere to either SOAP 1.1 or 1.2. It's not clear to me what benefits 1.2 provides over and above 1.1. This leads me to the conclusion that I should always use 1.1 to accommodate the largest number of compatible clients.
Why would I choose to create a SOAP 1.2 rather than a SOAP 1.1 web service?
From practical standpoint this is the case when you don't need SOAP1.2 if you're happy with 1.1, at least for now.
1.2 is quite different standard, its messages are infoset-based and (most notably) it is protocol-agnostic (you can use your own binary protocol for message delivery) and it is not backwards-compatible with 1.1.
You could read more here. Note the "Related information" section.
I am trying to make a call to a SOAP web service through Dojo, but have found no relevant, up-to-date documentation on how to make a SOAP request.
Does anyone have any experience making a SOAP request in Dojo?
IBM has something here. Unfortunately, it's not supported in Dojo. However, this library could be of use for JavaScript to SOAP connectivity.