WSA plugin: allow custom prefix for MessageID.#1351
Open
Merinorus wants to merge 1 commit intomvantellingen:mainfrom
Open
WSA plugin: allow custom prefix for MessageID.#1351Merinorus wants to merge 1 commit intomvantellingen:mainfrom
Merinorus wants to merge 1 commit intomvantellingen:mainfrom
Conversation
|
Any chance of getting this merged? It would solve a problem for me as well (I'm also trying to use the KvK Dataservice with python-zeep, like other participants in issue #975). Currently I need to keep a modified version of wsa.py around to make this work. |
This file contains hidden or 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.
Fix #975
Description
When using the WSA plugin, the header's field
MessageIDis created as follows:Some endpoints require the
urn:prefix to be absent:This PR allows you to specify the prefix you want with the WSA plugin. For instance, this fixes the author's problem in issue #975: