You are viewing a plain text version of this content. The canonical link for it is here.

Posted to xindice-dev@xml.apache.org by bu...@apache.org on 2004/09/24 13:17:24 UTC

DO NOT REPLY [Bug 31402] New: - Illegal tree crossing in org.apache.xindice.xml.dom.ElementImpl.getElementsByTagName

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31402>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31402

Illegal tree crossing in org.apache.xindice.xml.dom.ElementImpl.getElementsByTagName

           Summary: Illegal tree crossing in
                    org.apache.xindice.xml.dom.ElementImpl.getElementsByTagN
                    ame
           Product: Xindice
           Version: cvs head (1.1)
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: XML:DB API
        AssignedTo: xindice-dev@xml.apache.org
        ReportedBy: bnm77@lycos.de


In xindice-1.1b4, when getElementsByTagName is executed with a tag name not
existing in the element's child tree but in a sibling's child tree, the elements
are found in the sibling's tree and returned.
For example:
<abnahme>
<text>test</text>
</abnahme>
<abnahme>
<aenderungsdatum></aenderungsdatum>
<text/>
</abnahme>

If I execute getElementsByTagName("aenderungsdatum") when I'm on the first
"abnahme"-Element, the "aenderungsdatum" element is returned instead of null or
an empty NodeList.

Please have a look at it.