For some reason (I've never heard a convincing one), the DOM spec doesn't
say to return a node's text value when you use getNodeValue(). You have to
have to go down one more level into the node and get its text node, and
take that node's value. I don't have the C++ syntax handy, but it's
pro
Per the DOM spec
(http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1950641247),
Node.nodeValue is defined to return null for Document, DocumentFragment,
DocumentType, Element, Entity, EntityReference and Notation nodes. There is
not enough in your message to see if you are actually seeing some
Hi, I have a question and was wondering if any of you came across this
problem...
I am using DOMParser and to parse a XML string which I got it to do
correctly. Then I try to go though all nodes in the file using
DOM_Node::getNextSibling() method. I run into the problem when I try to
obtain a
Brian,
The patch to fix the potential leak of newStream created in
ReaderMgr::createReader() has been incorporated, please
help verify, thanks.
Regards,
Peiyong Zhang
XML Parsers Development
IBM Toronto Laboratory email: [EMAIL PROTECTED]
Pho
Team Xerces-C,
As I understand memory management in IDOM, the IDOM_Document allocates heap
memory for XMLCh* returned from such methods as IDOM_Element::getAttribute
and does not deallocate heap memory until the IDOM_Document destructor is
called.
So does this mean that the heap will grow unbound
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=3565
Thanks Curt - I'd be interested in reviewing and/or helping out when the
time is right. In the mean time has anybody got advice on the bReuseGrammar
flags. (I just learned how to spell grammar, doh) :)
Jim
> -Original Message-
> From: Arnold, Curt [mailto:[EMAIL PROTECTED]]
> Sent: Wed
Sandy Gao is working on a redesign of schema caching for Xerces-J and expects to be
visible pretty soon. When that design gets critiqued and functional in Xerces-J, then
it could be incorporated in
Xerces-C.
-
To unsubscribe,
Hi all - I have a question concerning performance improvement while doing
parsing with validation. We validate with a few schemas over and over again
in our server application. Currently we parse every time. I have been
looking into the breusegrammer parameter to DOMParser::parse but would like
Hi all,
We are trying to build the Xerces C++ library
on the Itanium IA-64-bits platform under Linux.
Compiling and linking, using g++ works fine.
But when running a standard sample like 'SAXCount', it crashes
when returning from the XMLBuffer destructor (XMLBuffer.hpp, line 126).
This only hap
Nouguier,
Kevin Philips has proposed a patch (simliar to yours), and
is available in
/src/util/NetAccessors/WinSock/BinHTTPURLInputStream.cpp v1.7,
please help verify, thanks.
Regards,
Peiyong Zhang
XML Parsers Development
IBM Toronto Laborato
hi,
I'm new on the list, and I hope my question will not raise The
flame...
About the bug
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1345, found in 1.4 of
xerces. It is still ( if it's a bug ... ) in 1.5.1. Is there reason for
that.
In all case, thanks a lot for xerces.
PS: I've
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=3567
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=3567
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=3565
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=3155
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=3422
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=3395
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=3513
19 matches
Mail list logo