xerces-j-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Glavassevich <mrgla...@ca.ibm.com>
Subject Re: DOM Load and Store parser filter & document element
Date Mon, 11 Apr 2011 17:28:49 GMT

Hi Konrad,

The document element (node) is never passed to an LSParserFilter. It says
that clearly in the Javadoc [1].

Please also note that you're not using Apache Xerces at all. The
implementation which ships in the Oracle JDK is a fork of the Apache code
base which Oracle/Sun has made all sorts of changes and additions to. If
you are experiencing issues with that code base you would need to pursue it
with Oracle. We have no influence over what they include in their versions.

Thanks.

[1]
http://xerces.apache.org/xerces2-j/javadocs/api/org/w3c/dom/ls/LSParserFilter.html

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org

"Schwarz, Konrad" <konrad.schwarz@siemens.com> wrote on 04/11/2011 12:17:29
PM:

> Hi,
>
> contrary to my reading of the DOM load and store specification, the
> document element node (that is, the top-level element at the root of
> an XML document, not the document node itself) is not being passed
> to my LSParserFilter's startElement() and acceptNode() methods.  My
> getWhatToShow() routine always returns 1, that is SHOW_ELEMENT.
>
> Is this a bug?
>
> I am using JDK 1.6_24 -- I think this incorporates Xerces.
>
>
> Regards,
> Konrad Schwarz
>
> Siemens AG
> Corporate Technology
> Corporate Research and Technologies
> CT T DE IT1
> Otto-Hahn-Ring 6
> 81739 M√ľnchen, Deutschland
> Tel.: +49 (89) 636-53579
> Fax: +49 (89) 636-45450
> mailto:konrad.schwarz@siemens.com
Mime
View raw message