IDOM getElementsByTagName

2001-09-13 Thread Smith, Cynthia J
I have not had any luck using getElementsByTagName for either an IDOM_Element* or for an IDOM_Document*. For example, the following fails for an IDOM_Document. IDOM_Document* pXMLDocument = parser.getDocument(); unsigned int elementCount = pXMLDocument->getElementsByTagName( XMLSt

Re: "Compiled" Schemas

2001-09-13 Thread Jason E. Stewart
"Murphy, James" <[EMAIL PROTECTED]> writes: > Tinny, thanks for the replay... I'm not clear on your statement below: > > > // Any grammar that is specified in anotherXmlFile is IGNORED. > > // AND there cannot be any internal subset in anotherXmlFile.. > > parser.parse(anotherXml

Re: IDOM memory management

2001-09-13 Thread Tinny Ng
delete myDocument is enough. Tinny Vinodkumar S wrote: > I have a small doubt in its memory management , let take an example like > this > // C++ IDOM - explicit deletion > IDOM_Document* myDocument; > IDOM_Node* aNode; > myDocument = IDOM_DOMImplementation::getImplementation()->createD

Re: "Compiled" Schemas

2001-09-13 Thread Tinny Ng
For "internal subset", I mean the DTD internal subset, i.e. something like ]> if the second "anotherXmlFile" has DTD internal subset, then you are not allowed to have reuseGrammar = true Sorry for the confusion, my description was intended as a generic usage information for both DTD

RE: IDOM memory management

2001-09-13 Thread Vinodkumar S
I have a small doubt in its memory management , let take an example like this // C++ IDOM - explicit deletion IDOM_Document* myDocument; IDOM_Node* aNode; myDocument = IDOM_DOMImplementation::getImplementation()->createDocument(); aNode = myDocument->createElement("ElementName"); myDocumen

Re: DOM_Node::getNodeValue() returns null string

2001-09-13 Thread Joseph_Kesselman
Some nodes -- Elements in particular -- have no nodeValue; to obtain their contents, you have to examine their children. See the DOM spec for details. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:

RE: "Compiled" Schemas

2001-09-13 Thread Murphy, James
Tinny, thanks for the replay... I'm not clear on your statement below: > // Any grammar that is specified in anotherXmlFile is IGNORED. > // AND there cannot be any internal subset in anotherXmlFile.. > parser.parse(anotherXmlFile, true); what do you mean by an "internal subset".

[DO NOT REPLY: Bug 3585] New: Plenty of ld warnings - symbols twice encountered

2001-09-13 Thread bugzilla
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3585

Re: IDOM memory management

2001-09-13 Thread Tinny Ng
> So does this mean that the heap will grow unbounded if > IDOM_Element::getAttribute is called repeatedly? Not really. Normally the getAttribute just return the same text value that is already saved inside the node. It doesn't allocate a new memory for the XMLCh* returned. Tinny "Houle, Denn

Re: "Compiled" Schemas

2001-09-13 Thread Tinny Ng
> In the mean time has anybody got advice on the bReuseGrammar > flags. The use of reuseGrammar for schema "should be" similar to DTD. You may want to give it a try and let us know if you found any bugs. to use reuse grammar, e.g.: // this is the first parse, just usual code as you do n