You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We received a WSDL with a targetNamespace attribute. That namespace has not been added to the WSDL with a prefix (as one usually would do). As such the WSDL contains messages where the parts have elements without namespace prefix.
This can be reproduced with modifying the existing samples in the tests (that have a prefix configured for the tns):
Currently the parsing fails (using latest version 3.39.0):
Caused by: java.lang.IllegalStateException: Invalid 'element' or 'type' attribute for message: getPetByIdRequest
at io.gatehill.imposter.plugin.soap.parser.Wsdl1Parser.getMessage(Wsdl1Parser.kt:276) ~[main/:?]
at io.gatehill.imposter.plugin.soap.parser.Wsdl1Parser.getInputOrOutput(Wsdl1Parser.kt:210) ~[main/:?]
at io.gatehill.imposter.plugin.soap.parser.Wsdl1Parser.getOperation(Wsdl1Parser.kt:188) ~[main/:?]
at io.gatehill.imposter.plugin.soap.parser.Wsdl1Parser.getBinding(Wsdl1Parser.kt:99) ~[main/:?]
at io.gatehill.imposter.plugin.soap.parser.VersionAwareWsdlParser.getBinding(VersionAwareWsdlParser.kt:94) ~[main/:?]
When getting the element attribute, the target namespace should be taken into account in function getAttributeValueAsQName
The text was updated successfully, but these errors were encountered:
driesva
added a commit
to driesva/imposter
that referenced
this issue
May 14, 2024
* Function to resolve the targetNamespace from the WSDL-document. If such a target namespace is declared and e.g. the element attribute of the message part has no namespace prefix, use that target namespace to construct a qualified name.
* Adapt random test WSDLs to have no namespace prefix
fixesoutofcoffee#569
* Function to resolve the targetNamespace from the WSDL-document. If such a target namespace is declared and e.g. the element attribute of the message part has no namespace prefix, use that target namespace to construct a qualified name.
* Adapt random test WSDLs to have no namespace prefix
fixesoutofcoffee#569
We received a WSDL with a
targetNamespace
attribute. That namespace has not been added to the WSDL with a prefix (as one usually would do). As such the WSDL contains messages where the parts have elements without namespace prefix.This can be reproduced with modifying the existing samples in the tests (that have a prefix configured for the tns):
Currently the parsing fails (using latest version 3.39.0):
When getting the element attribute, the target namespace should be taken into account in function
getAttributeValueAsQName
The text was updated successfully, but these errors were encountered: