HTTP/1.1 400 Bad Request on executing a WSDL with multiple bindings, portypes, or services.

4 Years Ago
JorgeR
MANAGEMENT CONSOLE

Summary

When the user designs a WSDL with multiple bindings, portypes or services, the response returns a 400 Error because Bizagi does not support the mentioned structures.

Applies to

Bizagi 10.x.

Symptoms

After the execution of a WSDL with multiple bindings, portypes or services, the response returns an error similar to:

HTTP/1.1 400 Bad Request
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-UA-Compatible: IE=Edge,chrome=IE8
Date: Thu, 18 Jun 2015 20:46:02 GMT
Content-Length: 0

Cause

Bizagi does not support requests in WSDL with multiple bindings, portypes, or services.

Solution

Split each bindings, portypes, or services in different WSDL and execute them separately.

Rate this Article:

Details

Last Modified:4 Years Ago
Last Modified By: Andread
Type: ERROR
Level: Intermediate
Article not rated yet.
Article has been viewed 5.3K times.

Options