Pierpaolo Fumagalli wrote: > I believe you're using a DOMParser, and you don't find a text node for > your & character. This is because an entity reference node is > inserted and this one has a child text node with the value of the &...; > thing.
Actually, Pier, the 5 built in entities are treated special in the DOM tree. EntityReference nodes are not created and the characters that they represent are inserted as plain text in the tree. Jim, I know that we had a bug in the first release of the Xerces parser where these entities simply disappeared. This was because the internal document handler can tell the underlying scanner to send text data as a Java char array or as a data index into the StringPool. The method that called out to the document handler was calling the wrong method which was being no-op'd by the DOMParser. Oops! We fixed this, though. What version of the parser are you using? Try 1.0.1 and see if your problem goes away. -- Andy Clark * IBM, JTC - Silicon Valley * [EMAIL PROTECTED]
