This repository has been archived by the owner on Dec 30, 2024. It is now read-only.
fromXMLname too restrictive #1
Open
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
… cause of tag like <my_xml_response>. Instead is better to search for a pattern were _x is specific followed by 4 hexdigits. All other _x matches should be ignored
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi.
I've found that the regexp used to find and replace some unicode in tagname yield wstools strictly bound to soap 1.2 specification.
A response from any soap service (< 1.2) could include tags like
<fn_retrieve_xml_pReturn> where the substring "xml" brings wstools to an unicodedecode error.
Any unicode should be addressed by specific 4 hexdigits: nothing more nothing less.
So a replaced regexp to somewat that allows xSOMETHING avoiding to try failing unicode substitutions.
hth.
alessandro.