Scott Cantor commented on XERCESC-1934:

I can see that behavior is embedded in the XMLScanner classes. The 
AbstractDOMParser overrides the namespace it reports when it turns the XMLAttr 
into a DOM AttrImpl. The SAX2 class seems to directly reflect the underlying 
XMLAttr objects from the scanner, which makes this either a riskier low level 
fix to the scanners, or a change with potential efficiency implications on the 
SAX2 code.

> SAX2 reports the xmlns attribute without a namespace
> ----------------------------------------------------
>                 Key: XERCESC-1934
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1934
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: SAX/SAX2
>    Affects Versions: 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.1.3, 3.1.4
>            Reporter: Boris Kolpackov
>             Fix For: 4.0.0
> When you have something like xmlns:foo="foo", SAX2 reports the 'xmlns:foo' 
> attribute as belonging to the XML namespace. However, if the namespace is 
> declared as xmlns="foo", the 'xmlns' namespace is reported as being 
> unqualified. Other parsers seems to be doing it in a more consistent manner.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to