AS7-6390 I think this is the most generic way of dealing with this probl... #1
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.
IMHO There is a problem with "http://xml.org/sax/features/namespace-prefixes" feature of SAX parser. When it is set to true attribute list of first element contains namespace definitions, moreover these attributes have parameters set incorrectly (at least AFAIK). So ...
there are parameters like:
{qname="xmlns:wsdl", uri="", local=""}
while it suppose to be:
{qname="xmlns:wsdl", uri="http://www.w3.org/2000/xmlns/", local="wsdl"}
Returning this namespace definitions as attributes causing they are processed once as "raw" attributes and then as namespace definitions. XALAN is checking for duplicated attributes based only on URI and local - so these two are different for IT.
I added lookup on qname if such URI/LOCAL lookup failed.