RE: parser-parse() question

2003-07-15 Thread Erik Rydgren
One way is to extend the allocator to provide a way to validate a pointer. The allocator has a list of large memory blocks which is chopped up into smaller bits when needed. It is a simple task to check if a pointer is contained inside a block. But that requires that the allocator is global. The

SV:RE: Help with xPath and DOM

2003-07-15 Thread Gröndal Daniel
Hi! Well, I guess I have to start using Xalan then. I can't always know the depth of the xPath expression, since the argument to countNodes is variable (i.e. user input). Getting the nodenames are probably an easy task (just need to parse the argument string for '/'), but since I don't know the

RE: parser-parse() question

2003-07-15 Thread Gareth Reakes
cheers Erik, I did not make that clear at all. Gareth On Mon, 14 Jul 2003, Erik Rydgren wrote: Gareth, you forgot to mention that the first document is still valid after a reset. The parser keeps the document in an internal list until the parser is deleted or the method resetPool is called

Re: SV:RE: Help with xPath and DOM

2003-07-15 Thread Gareth Reakes
Hi, or you can use Pathan (software.decisionsoft.com), an open source XPath module for xerces-c that my company maintains (soon to be XPath2!!). Gareth On 15 Jul 2003, Gröndal Daniel wrote: Hi! Well, I guess I have to start using Xalan then. I can't always know the depth of the

Re: parser-parse() question

2003-07-15 Thread Gareth Reakes
Hi, BTW, I asked this in a different thread (probably poor etiquette), and got the UserData answer. However, I'll bring it up again here since it is relatedis there any other way to tell if a node is still in memory or valid? I would like some sort of derefence mechanism to just do a

DO NOT REPLY [Bug 20353] - build error with bcc551 with XMemory.hpp

2003-07-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20353. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 20353] - build error with bcc551 with XMemory.hpp

2003-07-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20353. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

[Fwd: [vote] XMLBeans to enter XML incubation [was: Re: Vote forXMLBeans proposal in the XML Project (was RE: Vote for XMLBeans proposal)]](fwd)

2003-07-15 Thread Gareth Reakes
in case any other commiters have not seen this -- Gareth Reakes, Head of Product Development +44-1865-203192 DecisionSoft Limitedhttp://www.decisionsoft.com XML Development and Services -- Forwarded message -- Date: Wed, 09 Jul 2003 17:11:29 +1000

Re: Problem with XercesDOMParser setExternalSchemaLocation with space in path to the schema

2003-07-15 Thread greynolds
In case anyone is curious, we figured out the problem. Our actual path has spaces in 2 places and I had only replaced 1 of them for testing hitting head against wall. Replacing the spaces with %20 does indeed solve the problem. Geoffrey Reynolds I'm using the DOM Parser with an external

Re: parser-parse() question

2003-07-15 Thread elliot . rapp
So. If I try to operate on a node that has been released, it should still be in memory? Or, is it possible that I get some other node that is now using the memory freed up during that release? |-+ | | Gareth Reakes| | |

Re: C++ XML on OS/390?

2003-07-15 Thread Sherry_D_Bentz
David, Thanks for the info. It's just what I needed. Regards, Sherry Bentz David Cargill

Re: parser-parse() question

2003-07-15 Thread elliot . rapp
Thanks. OkI think I am finally beginning to understand the full story of release ;-) One more question though. The part that I still find confusing is how decisions are made about child nodes. For instancelets say that I load a document, get a reference to it, and get a reference to

C/C++ library (api's) to generate XML document

2003-07-15 Thread Rajan Bhide
Title: Message Hi, I require to generate XML document using XML document generator through my application code using C/C++ apis. I am trying this out using xerces C++ library for Solaris platform with CC compiler. The xerces-c.22.0.so library has a size of around 45MB, which is too much for

SV:C/C++ library (api's) to generate XML document

2003-07-15 Thread Gröndal Daniel
Hi! CC Cluster(nod1)% ls -l xerces-c_2_3_0-Sol2.7ForCC/lib/ total 11540 lrwxrwxrwx 1 40042535 ccuser17 Jul 14 10:13 libxerces-c.so - libxerces-c.so.23 lrwxrwxrwx 1 40042535 ccuser19 Jul 14 10:13 libxerces-c.so.23 - libxerces-c.so.23.0 -rwxr-xr-x 1 40042535 ccuser 5891704

RE: C/C++ library (api's) to generate XML document

2003-07-15 Thread Jesse Pelton
Title: Message I don't know if it's any smaller, but libxml is an alternative (http://xmlsoft.org). -Original Message-From: Rajan Bhide [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 12:54 PMTo: [EMAIL PROTECTED]Subject: C/C++ library (api's) to generate XML

RE: C/C++ library (api's) to generate XML documen t

2003-07-15 Thread Rajan Bhide
Hi Daniel, I suppose 40042535 indicates the file size in bytes which turn out to be 40 MB apporx. How r u finding it to be 5.9MB? -Rajan -Original Message- From: Gröndal Daniel [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 10:32 PM To: [EMAIL PROTECTED] Subject:

SV:RE: C/C++ library (api's) to generate XML documen t

2003-07-15 Thread Gröndal Daniel
Hi!! 40042535 is the owner of the file. The size is 5891704 approx 5.9MB... //daniel Rajan Bhide (2003-07-15 19:19): Hi Daniel, I suppose 40042535 indicates the file size in bytes which turn out to be 40 MB apporx. How r u finding it to be 5.9MB? -Rajan -Original Message- From:

RE: C/C++ library (api's) to generate XML documen t

2003-07-15 Thread Rajan Bhide
Hi, Here is my o/p of $)ls -l drwxr-xr-x 2 rbhide users 512 May 8 18:54 SunWS_cache lrwxrwxrwx 1 rbhide users 69 Jun 6 20:21 libxerces-c.so - /home/rbhide/utilities/xerces/xerces-c-src2_2_0/lib/libxerces-c.so.22 lrwxrwxrwx 1 rbhide users 71 Jun 6 20:21

RE: C/C++ library (api's) to generate XML documen t

2003-07-15 Thread Jesse Pelton
I'm a Windows developer, so what I'm about to ask may be dumb. Is there any possibility that your library includes debugging symbols? -Original Message- From: Rajan Bhide [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 1:36 PM To: [EMAIL PROTECTED] Subject: RE: C/C++ library

RE: C/C++ library (api's) to generate XML documen t

2003-07-15 Thread Scott Cantor
I'm a Windows developer, so what I'm about to ask may be dumb. Is there any possibility that your library includes debugging symbols? Yes, that's his problem. Debug builds of C++ on Solaris are enormous. Well, even Linux is, but Solaris is really big. -- Scott

SV:RE: C/C++ library (api's) to generate XML documen t

2003-07-15 Thread Gröndal Daniel
Hi! Strange, but there might be (must be, of course) some kind of difference between the builds. Did you download the source and compiled it yourself? In that case there might be a difference depending on the compiler perhaps... I think what I have installed is the Xerces-C++ 2.3 32 bit Binary

RE: RE: C/C++ library (api's) to generate XML doc umen t

2003-07-15 Thread Rajan Bhide
Hi again, Yes I downloaded the source code and complied it using the -g i.e. debug flag whith FORTE C++ complier(CC) for Solaris. If this is the reason then I would try with a non debug build. But then Again my question remains unanswered (expect for libxml suggestion) that Can I build a lib

DO NOT REPLY [Bug 21623] New: - XMLParsePathToFSSpec fails due to file not found

2003-07-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21623. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 21527] - Misleading Cygwin Build Outputs

2003-07-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21527. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.