Created: 09/Oct/10 Updated: 28/Oct/11 Resolved: 28/Oct/11
Status: Project: Component/s: Affects Version/s:
Closed Mirth Connect Administrator 2.0.0
Fix Version/s: Type: Reporter: Resolution: Labels: Remaining Estimate: Time Spent:
None Bug Nico Vannieuwenhuyze Duplicate None Not Specified
Priority: Assignee: Votes:
Minor Gerald Bortis 0
Original Estimate: Issue Links:
Not Specified Not Specified
duplicates MIRTH-1790 Add support for multiple services and... Closed
When generating a soap envelope for a .NET web service that exposes a soap 1.1 binding as well as a soap 1.2 binding, Mirth Connect selects the soap 1.2 port/binding but generates an envelope containing the soap 1.1 namespace (xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/") instead of the 1.2 namespace (xmlns:soap="http://www.w3.org/2003/05/soap-envelope"). When calling the web service with this configuration, you get an error that the web service is not a soap 1.2 web service.
Comment by Gerald Bortis [ 06/Jan/11 ] Do you have an example of a public WSDL that causes this issue? Comment by Gerald Bortis [ 14/Jan/11 ] This should have been fixed as part of . Comment by Jacob Brauer [ 16/Mar/11 ] This will be fixed when is fixed. When there are multiple ports, one may be soap 1.2 and one may be soap 1.1. Only one of those is used for envelope generation, and one of those (not necessarily the same one) is used to fill in the port field. Comment by Jacob Brauer [ 28/Oct/11 ] Duplicate of
Generated at Tue Feb 09 20:33:24 PST 2016 using JIRA 6.2.7#6265 sha1:91604a8de81892a3e362e0afee505432f29579b0.