Re: FormatPrettyPrint implementation

Comment: I'd hate to see any implementation of FormatPrettyPrint go in that does not take account of the DTD/Schema.  Without the DTD/Schema one cannot make any safe assumption about the content of the document (eg ignoring whitespace nodes, inserting new lines etc). Maybe there needs to two fea

RE: FormatPrettyPrint implementation

I was unaware that some work at already been done. I tried to apply the patch that is referenced below but keep getting errors. What version of the files is the diff against? -Kevin At 09:26 AM 11/21/2002 -0500, you wrote: See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13840 for anothe

RE: DOM Validation of XML against a schema

With the help of Philippe and a DOM sample I constructed the program shown below.  I find the exception stratgy usefully to detect really exceptional conditions as stated in the API doc, for example - a malformed xml header.   I am still struggling however to understand how to detect logica

Re: Parse Error first time, but works second time

Try using the sample SAXCount and pass in your xml file as parameter twice, i.e. SAXCount testhaserror.xml testhaserror.xml see if you can see the error twice, if so, then it may be your program problem. Tinny - Original Message - From: "Zach Lute" <[EMAIL PROTECTED]> To: <[EMAIL PR

Parse Error first time, but works second time

I am currently using Xerces 2.1.0 (compiled under gcc 3.2) in a project. I have set up the parser with a basic error handler (throw an exception, print out a message), etc. I am now having the strangest problem. If I try to parse a document, I get a parse error. If I then try to parse the same

Re: DOM Validation of XML against a schema

Hello, You could define an ErrorHandler and then try something like this before parsing :     parser->setErrorHandler(myErrorHandler);     parser->setValidationScheme(XercesDOMParser::Val_Always);     parser->setValidationSchemaFullChecking(true);     parser->setDoNamespaces(true);     parser-

DOM Validation of XML against a schema

> How do I validate XML against a schema when parsing using DOM as in: > > pDomDocument = pDOMBuilder->parse( domInputSource ); > > I have schemas for the simple XML files in the domInputSource and am mainly >interested in getting useful structure/content error messages at parse time. > >

RE: FormatPrettyPrint implementation

See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13840 for another implementation. -Original Message- From: Kevin King [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 2:12 AM To: [EMAIL PROTECTED] Subject: FormatPrettyPrint implementation Hello, I should probably first

RE: Xerces-C, ICU, and Mac OSX

Actually this is even easier than you think as ICU is already supported on Mac OSX. :) I'll see if I can do this work sometime in February 2003. Bob > -Original Message- > From: James Berry [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 20, 2002 11:34 PM > To: Xerces C Dev; Robe

Re: FormatPrettyPrint implementation

Hi, nice work :). The spec does not say how the pretty printing should work so if no one has any objections to the way you have done it then I suggest we commit it and see what users say. I know many people ask for this functionality. Gareth On Thu, 21 Nov 2002, Kevin King wrote: >

RE: Memory growth in DOM

Hi, On Wed, 20 Nov 2002, Bagepalli, Kiran wrote: > Hi Gareth, > Thanks for the clarification. > Still have a few more things to clarify. > 1. Is the problem relating to releasing attributes limited to ID > attributes because thats what bugzilla says or this > problem will occ

RE: XPath Support in Xalan1.4 using Xerces 2.1 DOMNode

Hi, Pathan 2 works with xerces 2 but is pre alpha. Pathan 1 is in the process of being converted. It now fully works (we hope) with Xerces 2 but leaks loads of memory (changing from DOMString to XMLCh). If you can put up with this until it is fixed in a couple of weeks then check out the

DO NOT REPLY [Bug 14723] - Memory leak in atomicOpsMutex

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu