Re: NEWBIE: getNextSibling Still not working

Well, you can use an alternative... You can get all the childnodes as in; children = parent.getChildNodes(); for (x = 0 ; x < children.getLength() ; x++) { child = children.item(x); } This is just an alternative though of the getNextSibling() problem - - - RYAN B. ROLEDA

Re: comments outside root

> At 7:20 PM 3/26/2001, Chris Hill wrote: >> I don't think comments are even exposed via SAX events, so this would not >> be an issue. There is no SAX comment event to suppress. Or is there? Comments are exposed via LexicalHandler in SAX. Xerces-C++ 1.4 does implement LexicalHandler.

RE: comments outside root

> When you speak of better performance, are you > referring to the extra function call to the > advanced handler? The SAX API is just generally higher overhead than the internal interface, because it requires that the SAXParser handle the internal event callbacks, then just turn around and pass

RE: comments outside root

At 05:21 PM 3/26/2001, Dean Roddey wrote: >I think that this is a SAX convention, which is why the suppression was >added. If the SAX spec says that such events won't show up, we can't send >them because it could seriously freak out applications written to the SAX >spec. I don't think comments ar

RE: comments outside root

My guess is that comments slipped through the cracks. Processing instructions (PIs) were originally (Xerces 1.2?) ignored outside of the root element, but after some pestering I got the code changed to make sure this wasn't so (since I really wanted to use a PI before the root element. I think D

insert xml data into databse ??

-Original Message- From: Dean Roddey [mailto:[EMAIL PROTECTED]] Sent: Monday, March 26, 2001 5:24 PM To: '[EMAIL PROTECTED]' Subject: RE: tools for generating XML document Generating XML doesn't really need much in the way of tools. If you have some proprietary data format, even if th

RE: tools for generating XML document

Dean, thank you very much -Original Message- From: Dean Roddey [mailto:[EMAIL PROTECTED]] Sent: Monday, March 26, 2001 5:24 PM To: '[EMAIL PROTECTED]' Subject: RE: tools for generating XML document Generating XML doesn't really need much in the way of tools. If you have some propriet

RE: tools for generating XML document

Generating XML doesn't really need much in the way of tools. If you have some proprietary data format, even if there was a tool you'd have to write some code of some sort to massage it such that the tool could understand it. By that point, the extra step to just generate the document yourself (and

RE: comments outside root

I think that this is a SAX convention, which is why the suppression was added. If the SAX spec says that such events won't show up, we can't send them because it could seriously freak out applications written to the SAX spec. We could argue that the advanced handler, since its already outside of

tools for generating XML document

Hi, i got a requirement in which i have to generate on the fly XML documents from some propritery data. do we have any tool at first place which generates XML documents on the fly ?? Thanks Anand -Original Message- From: Chris Hill [mailto:[EMAIL PROTECTED]] Sent: Monday, March 2

comments outside root

My advanced handler (XMLDocumentHandler) wasn't receiving docComment events for comments outside the root element, so I took a look at SAXParser::docComment, and it is intentionally suppressing the events. Is there any particular reason that comments outside the root are suppressed? Processi

RE: Bug report and fix

Yes, this is well known. We never fully implemented the standalone checks, because they are very high overhead relative to the number of people who seem to need to use them (basically almost no one so far, since I can't remember anyone complaining about it.) And I assume that you are just reportin

[Bug 1122] Changed - cannot unpack the tar ball

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1122 *** shadow/1122 Mon Mar 26 13:33:43 2001 --- shadow/1122.tmp.15329 Mon Mar 26 14:01:19 2001 *** *** 2,9 | cannot unpack the tar ball | +---

[Bug 1122] New - cannot unpack the tar ball

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1122 *** shadow/1122 Mon Mar 26 13:33:43 2001 --- shadow/1122.tmp.15235 Mon Mar 26 13:33:43 2001 *** *** 0 --- 1,26 + ++ + | cannot unpack the

Re: Domprint and overwriting files

Emma I might be able to get you in the right direction. I needed to write out to a file instead of to stdout. Here is what I changed. Please note that this is not thoroughly tested. First, I changed the constructor to DOMPrintFormatTarget to pass it an ostream and added a class member as well

Re: Serializer Question

Andy I asked about the serializer since I saw mention of it in the archives ([EMAIL PROTECTED]) and nothing since. I didn't want to reinvent the wheel. Todd >From: "Andy Heninger" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: <[EMAIL PROTECTED]> >Subject: Serializer Question >Date:

Bug report and fix

Hi, there, The current XML4C ACCEPTS the test case (shown below) and therefore FAILS on validity constraint: Standalone document declaration. Validity constraint: Standalone Document Declaration The standalone document declaration must have the value "no" if any external markup dec

RE: Query on xerces-c_1_1 parser

If you say "UTF-16", the parser will figure out what endianess. To do this, it must have either a BOM or an XMLDecl or both. -- Dean Roddey Software Geek Extraordinaire Portal, Inc [EMAIL PROTECTED] -Original Message- From: Bill Schindler [mailto:[EMAIL PROTECTED]] Sent: Mo

ICU 1.8 for Xerces-C

I have updated the xerces-C packageBinaries.pl script to work with the new release of ICU 1.8 on Windows. For more information on ICU 1.8 see http://oss.software.ibm.com/icu/ Part of the packageBinaries script edits the Windows MSVC project file to build with ICU. Even if you are building by h

Re: Query on xerces-c_1_1 parser

> 1. Does xerces-c_1_1 support encoding="UTF-16" ? >Because I tried this encoding and results were > negative. Try adding the endian -- "UTF-16LE" (for little endian) or "UTF-16BE" (for big endian). If I remember correctly, some UTF-16 related bugs were fixed recently. Xerces 1.4 is probab

RE: Casting DOM_Node to DOM_Element

> The solution 1 (cast operator): > class DOM_Node > { > ... > operator DOM_Element(void); > }; > > The solution 2 (cast constructor): > class DOM_Element > { > ... > DOM_Element (const DOM_Node&); > }; > I think I would prefer the cast operator since that would most cle

RE: xerces

Thanks a lot man. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, March 26, 2001 11:58 AM To: [EMAIL PROTECTED] Subject: Re: xerces Elements have no nodeValue; you have to examine their children. See the DOM specification, available at http://www.w3.

Re: xerces

Elements have no nodeValue; you have to examine their children. See the DOM specification, available at http://www.w3.org/DOM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Serializer Question

Todd Firsich asks > I am having trouble following the thread on Serialization for Xerces since I > only have the mailing list of 2000 and since last week ... what is the state > of the serializer? I need to add to DOMPrint the ability to write to a file > instead of to stdout and I am stuck. A

Query on xerces-c_1_1 parser

Hi, I am using the xerces-c_1_1 parser in a VC++ application. I have certain doubts to be clarified. Hope you could help me out. 1. Does xerces-c_1_1 support encoding="UTF-16" ? Because I tried this encoding and results were negative. 2. If NO, does any of the later versions support this en

xerces

Hi, I have a technical question. I am using the DOMParser to parse the xml file. It parses the file and builds the DOM_Document just fine. It also works when I ask for any node in the tree, but for some reason it fails when I call getNodeValue() function to get the value of the node, although t

RE: Casting DOM_Node to DOM_Element

Hi, Dave, Thanks, I noticed that a dom element constructed by DOM_Element() will compare == to 0 (similar to java's null object reference variable), this is what I am looking for. Regards, Peiyong Zhang XML Parsers Development IBM Toronto Labo

asserts in Xerces

Hi! We have had some problems in our production environment with the (prebuilt) Xerces lib version 1.4 for AIX 4.2. On some large (5.4 MB) files, the lib asserts at this location in NodeVector.cpp: void NodeVector::init(unsigned int size) { assert(size > 0); data = new NodeImpl *