RE: Problems with XML files...

look at the MemParse sample code -Original Message-From: João Marcelo Loureiro do Amaral [mailto:[EMAIL PROTECTED]]Sent: Wednesday, June 27, 2001 12:45 PMTo: Ryan B. RoledaCc: [EMAIL PROTECTED]Subject: Re: Problems with XML files...Dear Ryan,     I'd like you help

RE: Separate MemBufInputSource as input

Also, since you are reading from a file, should you not be using the LocalFileInputSource class instead .. that should hopefully take care of very large xml files ... > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 22, 2001 10:23 AM > To: [E

RE: Support For Hp-Ux 10.2 and solaris 2.8

source code compiles on Solaris 2.8 and works ... don't know about hp-ux 10.2 > -Original Message- > From: Aniruddha Shevade [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 20, 2001 2:14 PM > To: [EMAIL PROTECTED] > Subject: Support For Hp-Ux 10.2 and solaris 2.8 > > > Hello > We ar

RE: What is IDOM?

the documentation is there on the xml home page at http://xml.apache.org/xerces-c/program.html#IDOMProgGuide > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 20, 2001 10:15 AM > To: [EMAIL PROTECTED] > Subject: What is IDOM? > > > Having

RE: DOMParser does not report errors for XML that are not well-fo rmed

Thanks folks. As for the MemParse example, the first line had scrolled off the screen and I was missing out on seeing the error message that is the first line of the output of the MemParse code. > -Original Message- > From: Erik Schroeder [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 1

RE: DOMParser does not report errors for XML that are not well-formed

Peter, You could also try this out with the MemParse sample code that comes along with the package. If you modify the string in gXMLInMemBuf variable in MemParse.cpp from a well-formed XML string to a not well-formed one and try running the sample code, you will see the behavior that I am seeing.

RE: Xerces 1.2.0

When one calls the getDocument() on a parser instance, one is getting back a reference to the DOM_Document member of the parser. And since Xerces has a reference counting mechanism, your document reference should be fine even if your parser instance goes out of scope. (people, correct me if

DOMParser does not report errors for XML that are not well-formed

I am using a DOMParser instance to load XML from a string or a file to a DOM by calling the parse(InputSource...) method on the string. When the XML string is not well-formed, I do not get any exceptions (I am catching XMLException while parsing). So I looked at the MemParse sample code which us

RE: Problem building code on Solaris

We are using Xerces on Solaris 8 and it builds succesfully. We built it using Forte 6. Of course, it was not success on the first go but after some digging we got it to work. So if you have not done the following, then it may be worthwhile trying out it first: 1> Run the script runConfigure as fo

RE: Xerces 1.2.0

Sometime back, I had put out a multi-threaded test code that failed for a multi-cpu Sun box (after I had already read the Xerces FAQ). Later, we discovered that the code crashed not due to a multi-threaded env but due to some memory management problems within Xerces (we were actually straining the

Segmentation fault in a multi-threaded usage of Xerces-C

We are using Xerces-C1_4 on a two-processor Sun box running Solaris 8. There appears to be no problem in a single-threaded app, however, a multi-threaded app fails. I have created a test code that makes simple Xerces calls and which fails in a multi-threaded environment. The test code can be run i

RE: Xerces alias names for the various encodings?

I think XMLUni.hpp is the file to look at for the definitions. > -Original Message- > From: Mark A Russell [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 04, 2001 1:54 PM > To: Xerces C++ Mailing List > Subject: Xerces alias names for the various encodings? > > > Anyone know what the a

RE: Stopping a SAX, Mail archive down

I have not tried this ... but the parseFirst() and parseNext() calls of the SAXParser class are something that may give you some lead > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 03, 2001 3:35 PM > To: [EMAIL PROTECTED] > Subject: St

RE: [Bug 1446] New - Problems with replaceChild & appendChild

If you are not making a call to DOM_Document::importNode() before adding adding a DOM_Node from another DOM_Document, then thats not correct. Using importNode() should solve your problem... as far as I know, this is not a bug. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAI

RE: Deleting char* returned from DOMString.transcode() in VC++ 6.0

Title: Deleting char* returned from DOMString.transcode() in VC++ 6.0  select  "Debug Multithreaded DLL".

ignore whitespace in non-validating parser

Is it possible for a "non-validating" parser not to include ignorable whitespace such as tabs, carriage returns etc. If so, then how does one go about it? If I got it right, the setIncludeIgnorableWhitespace(bool) is effective only for a validating parser Thanks. ---