SOAP component generates wrong request body

[Glico21]

SOAP component generates wrong request body

Description

When you try to generate a sample SOAP request, after configuring the component and specifying the WSDL URL, Binding, Operation you get the schema of the object and proceed to fill the fields in the Mapping section. The Bug is that the integrator automatically generates an object named parameters based on the data schema of an object with a different name.

Such an object results in an error: io.elastic.soap.exceptions.ComponentException: Can not find valid structure for request. Object 'GetData' is not exist

For example, in the case shown in the screenshot, the object should contain the name GetData as represented in Operation.

Component Version

[
v1.2.9 - Apr 8 2022, 19:29rev: ca3982b
And lower
]

Steps to Reproduce

1. Choose SOAP v2 component
2. Fill WSDL URL (For example http://www.dneonline.com/calculator.asmx?WSDL), Binding, Operation
3. Request body automatically creates object parameters
4. Try to get a sample
5. Get error "Object %NAME% is not exist

Actual Result

The integrator generates object parameters instead right one.

Expected Result

Integrator generates object with right name from Operation name according to schema.

Workaround(s)

It is possible to go to code mode and change object name to right one

You can test this issue in the test flow in Academia