[ 
http://issues.apache.org/jira/browse/XERCESC-1377?page=comments#action_62394 ]
     
David Bertoni commented on XERCESC-1377:
----------------------------------------

I believe, per the reporter's email to the list, that this is not bug in the 
SAXParser class, since it does not support namespace-aware parsing.

Does anyone object to marking this as invalid?  Perhaps we need to update the 
documentation to make it clear that XMLDocumentHandler calls, when used with 
SAXParser, will not provide correct namespace information?

> Error in SAXParser! invalid namespaces
> --------------------------------------
>
>          Key: XERCESC-1377
>          URL: http://issues.apache.org/jira/browse/XERCESC-1377
>      Project: Xerces-C++
>         Type: Bug
>   Components: SAX/SAX2
>     Versions: 2.6.0
>  Environment: Windows XP
> Borland Builder 6
>     Reporter: Vadim Shapovalov
>     Priority: Blocker

>
> <?xml version='1.0' encoding='utf-8'?>
>       <root>
>               <node1 xmlns="ns1">
>                       <node2 xmlns="ns2">
>                               <c1/>
>                               <node1> <!-- this node must belong to ns2 not 
> to ns1 -->
>                                       <c2/>
>                               </node1>
>                               <c3/>
>                       </node2>
>               </node1>
>       </root>
> SAXParser tells me that root/node1/node2/node1 has ns1 namespace. it`s not 
> good!!!
> Note that c2 has right ns2 namespace.
> I used version 2.0 and there was no such a bug there.
> If you cant fix it quickly, please tell me how to fix or avoid this bug.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to