DO NOT REPLY [Bug 24371] - dom parser would crash without warning when parsing an ill-formed xml document

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

RE: Too big for Embedded systems

Good to know. Useful open source projects never die. According to the mailing list archives, there are at least a few people attempting to use expat on embedded systems. No clear indications of how successful they've been, though. > -Original Message- > From: David Parker [mailto:[EMAIL

RE: Too big for Embedded systems

Thanks for the input. I needed to more specific, my fault. 1) The embedded platform is C++ on a ARC MQX Precise RTOS( any java solution is out ) 2) Definitely open source - the unicoi list price is about $19K and allegrosoft is about $5K 3) It would be best if it were a pair: Sche

RE: Too big for Embedded systems

Expat got moved to SourceForge: http://sourceforge.net/projects/expat/. > -Original Message- > From: Jesse Pelton [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 05, 2003 3:31 PM > To: '[EMAIL PROTECTED]' > Subject: RE: Too big for Embedded systems > > > Well, there's James Clark'

RE: Too big for Embedded systems

Well, there's James Clark's expat (which I don't think is maintained any more), and MinML (Java - see http://www.wilson.co.uk/), and JAXP (also Java - http://www.gnu.org/software/classpathx/jaxp/), and RomXML (http://www.allegrosoft.com/romxml.html), and the XML MicroParser (http://www.unicoi.com/D

Re: link failure on os/x with xerces cvs revision

I'm the responsible party for the Mac OS X port, but confess I've been a little less than responsible of late. A few notes: - As noted by somebody, the ProjectBuilder (and also CodeWarrior) projects haven't yet been brought up to date with late changes in the cvs. I'll be doing that soon. I'l

Too big for Embedded systems

Hello, I'm trying to find an open source XML parser for a Motorola 5282. It needs to be about 20-100Kbytes of code. Does anybody know what size Xerces takes? Or any other XML parsers for embedded systems. -bill --

Re: Append Child, Insert Before, Remove Child, and Replace Child

> Actually I had already read that and found it to be somewhat ambiguous. > > Method: Append Child > Adds the node newChild to the end of the list of children of this node. If > the newChild is already in the tree, it is first removed. > Parameters: > newChild of type Node > The node to a

Re: Append Child, Insert Before, Remove Child, and Replace Child

ThanksI really appreciate it. It was that little bit of ambiguity that was causing me trouble. |-+> | | Neil Graham | | | <[EMAIL PROTECTED]| | | >| | |

DO NOT REPLY [Bug 24439] - XMLFormatter Constructors changed in 2.3.0 - not in documentation

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

Re: Append Child, Insert Before, Remove Child, and Replace Child

Hi Elliot, Although I agree with you that the spec is not crystal-clear on this point, my intuition is that implementations need to return a node that is isomorphic to the one that's been added, but, at their discretion, this doesn't have to be identical. If I were you and this were important

RE: Append Child, Insert Before, Remove Child, and Replace Child

Thanks! I had looked into this somewhat but was a little leery b/c it is marked experimental for 2.2 (which I think I am locked into using). Also, I am just about beta and not too excited about such a fundamental change. Plus, in the end I would still rather not create another node at all if

Re: Append Child, Insert Before, Remove Child, and Replace Child

Thanks for the reference! Actually I had already read that and found it to be somewhat ambiguous. Method: Append Child Adds the node newChild to the end of the list of children of this node. If the newChild is already in the tree, it is first removed. Parameters: newChild of type Node

DO NOT REPLY [Bug 24439] New: - XMLFormatter Constructors changed in 2.3.0 - not in documentation

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

Re: Append Child, Insert Before, Remove Child, and Replace Child

> Don't everybody answer at once ;-) > > I apologize if this question is obvious or inappropriate, but it is a > behavior of the parser that I haven't been able to definitively classify > yet. So, if anyone could offer any help I would really appreciate it. The DOM recommendation will answer

RE: Append Child, Insert Before, Remove Child, and Replace Child

How about using the DOM UserData mechanism to store each of your wrapper nodes against the node that it wraps. This way, before you make a new wrapper node, you can check if you already have one for that node and use it instead. As an added benefit, you can also register a UserDataHandler that w

Re: Append Child, Insert Before, Remove Child, and Replace Child

Don't everybody answer at once ;-) I apologize if this question is obvious or inappropriate, but it is a behavior of the parser that I haven't been able to definitively classify yet. So, if anyone could offer any help I would really appreciate it. The reason that is an issue for me is that I

Re: link failure on os/x with xerces cvs revision

I edited out the 'inline' from those two methods and my linking problem went away. So, I suspect there's some kind of issue with gcc 3.3 on os/x here. Do they really need to be inline?... Inline in the .cpp file. Kinda odd. Here's the diff I don't have commit rights, so could someone with acces

Re: link failure on os/x with xerces cvs revision

Can't give you an answer but I too am very interested to learn how to build Xerces on OS X. I've tried it with the provided ProjectBuilder project and that didn't work. Don I just built Xerces from CVS on OS/X (10.2) with gcc3.3 and it compiled ok, but my app didn't link. (It linked ok on RH9).

link failure on os/x with xerces cvs revision

I just built Xerces from CVS on OS/X (10.2) with gcc3.3 and it compiled ok, but my app didn't link. (It linked ok on RH9). I get these unresolved symbols... ld: Undefined symbols: xercesc_2_3::XMLGrammarPoolImpl::getURIStringPool() xercesc_2_3::XMLGrammarPoolImpl::getXSModel() const ..I note that t

RE: Parser

Title: Message It looks correct to me. Do you really see #text nodes while traversing the tree through iterator->nextNode() ? That is weird. Now I’m all out of answers. Sorry.   / Erik   -Original Message- From: Milan Tomic [mailto:[EMAIL PROTECTED] Sent: den 5 november 200

RE: Parser

Title: Message       I'm using this:   DOMNodeIterator* iterator = theDOM->createNodeIterator(rootElem, DOMNodeFilter::SHOW_ELEMENT, NULL, true);       but I still see #text "nodes". Am I missing something? I'd like to see only real elements (i.e. ), nothing else.   Thank you.     ---

RE: Parser

Title: Message Use the createTreeWalker method or createNodeIterator method on the DOMDocument.   / Erik   -Original Message- From: Milan Tomic [mailto:[EMAIL PROTECTED] Sent: den 5 november 2003 13:04 To: [EMAIL PROTECTED] Subject: RE: Parser     Thank you.  

Re: parsing strings

Sean,   Sorry for late replying.   When you sent this message I had already found a similar solution. Now I test your solution and it also works fine.   Thanks a lot anyway.   Carlos Sean Kelly <[EMAIL PROTECTED]> wrote: On Fri, 24 Oct 2003, [iso-8859-1] Carlos Bazílio wrote:>> I'm a newbie at Xerc

RE: Parser

Title: Message   Thank you.   > easiest is to create a tree iterator that doesn’t show text nodes while traversing the DOM tree.   How can I do that?   Milan     -Original Message-From: Erik Rydgren [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2003 12:58 PMTo:

RE: Parser

Title: Parser That is standard DOM behavior. The carage-return line-feed characters you have mixed into the XML are treated as non ignorable text content. Hence text nodes are created. There are several ways to solve your problem but the easiest is to create a tree iterator that doesn’t s

Parser

Title: Parser     I'm iterating through nodes: tmpNode = (DOMElement*)tmpNode->getChildNodes()->item(atoi(nodePos.c_str()));     but I got some strange "tags" with "#text" name when parser found $0D$0A bytes between two tags. How can I disable this? I'd like parser to retrive only valid