With the recent changes in 18c4c6a, it actually breaks with the WSDL I'm using so I thought I'd run the tests to confirm and I noticed that the spec was expecting the incorrect message tag. Not sure if this needs to be merged in considering it appears that the WSDL I'm using may not be standards compliant.
Hello from the future! I am doing some housekeeping and noticed this change is already in the main branch, so I am closing this PR. Thank you for your contribution.
With the recent changes in 18c4c6a, it actually breaks with the WSDL I'm using so I thought I'd run the tests to confirm and I noticed that the spec was expecting the incorrect message tag. Not sure if this needs to be merged in considering it appears that the WSDL I'm using may not be standards compliant.
Examples can be seen here.