[FIX] multiple nested complex types expecting "any" and receiving etree._Element input #1384
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is an issue when the WSDL consists of multiple nested complex types and expects an "any" input, and you attempt to provide the input as an
etree._Elementobject.On the
rendermethod it was always expected that the value received was a dictionary. However, in this specific scenario, the "any" element is represented as an etree._Element, resulting in the element_value receiving theNotSetvalue. As a consequence, this situation triggers an exception: zeep.exceptions.ValidationError: Missing element for Any.The WSDL where this issue was encountered is structured as follows: