The SOAP engine wraps the parameters in an element named after the operation (<tns:GetItem>). That matches what WCF and JAX-WS generate, but a document/literal WSDL can declare a different input element (<tns:GetItemRequest>), and then the service answers "unknown operation".
The fix is to take the element name from the operation's input message part in the WSDL when it's available, and fall back to the operation name. Parser: packages/backend/src/connectors/parsers/wsdl.parser.ts, engine: soap.engine.ts. A test with a small WSDL fixture of each style would be ideal.
The SOAP engine wraps the parameters in an element named after the operation (
<tns:GetItem>). That matches what WCF and JAX-WS generate, but a document/literal WSDL can declare a different input element (<tns:GetItemRequest>), and then the service answers "unknown operation".The fix is to take the element name from the operation's input message part in the WSDL when it's available, and fall back to the operation name. Parser:
packages/backend/src/connectors/parsers/wsdl.parser.ts, engine:soap.engine.ts. A test with a small WSDL fixture of each style would be ideal.