fix: handling attributes on the body tag in the server for both rpc and document styles #814
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.
Description
When adding attributes to the body tag (e.g.
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
), the library currently returns the following error:Currently, this was only supported using the document style and when the attributes key was set to the default "attributes". This update adds support for rpc style as well and updates the document style to get the key from the server options.
Related issues
Checklist
Obs. I could not find a way to send an attribute on the body tag from the client or any test that covered the same scenario for the existing supported case (document style and attributesKey set to default "attributes"), so that's why no new unit tests were added.
guide