"Tinny Ng" <[EMAIL PROTECTED]> writes: > I didn't encounter this before. And the problem only arise if using > Xerces-Perl, but not with Xerces-C++ directly, right?
Yes, correct. Here's some more info. During the parse the Document is configured correctly, but when I leave parse() and invoke getDocument() the Document has changed. getFirstChild() returns the bogus comment node because the node list is somehow messed up, I need to dig further for this. However, getDocumentElement() returns the root node just fine. My real trouble is that I stepping through the code in GDB, and I don't have a lot of experience debugging Xerces-C, so printing out XMLCh* arrays was a bit of a pain, but I wrote some debug routines that are helping. Any tipes you can give for debugging will be appreciated. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
