Entity reference causes multiple (split) child nodes

Question

Version: CXML Parser V.1.0.1
In the following ---
<GeneSymbol>TGF-&;bgr;</GeneSymbol>
---the data is returned as THREE child ("#text") nodes instead
of the expected one: (1) contains "TGF-", (2) contains "&", and
(3) contains "bgr;". I expected (and wanted) the data to come
back in one node.
Is this my mistake or the parser's?
(I have encountered the same problem in other examples, like
"administration &; dosage". I get three nodes instead of
one node with "administration & dosage".
Don Nelson
Contractor
Natl Library of Medicine
null

Answer 1

Donald Nelson (guest) wrote:
: Version: CXML Parser V.1.0.1
: In the following ---
: <GeneSymbol>TGF-&;bgr;</GeneSymbol>
: ---the data is returned as THREE child ("#text") nodes instead
: of the expected one: (1) contains "TGF-", (2) contains "&", and
: (3) contains "bgr;". I expected (and wanted) the data to come
: back in one node.
: Is this my mistake or the parser's?
: (I have encountered the same problem in other examples, like
: "administration &; dosage". I get three nodes instead of
: one node with "administration & dosage".
: Don Nelson
: Contractor
: Natl Library of Medicine
The DOM spec requires that there is one text node for each block
of text. So, this should be considered a bug and will be fixed
in a future release of the parser. In the meantime normalize()
can be used on elements as a workaround.
The SAX spec allows multiple calls to characters() for each
block of text so it is working correctly.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null