RE: corrupt archive

I experienced the same problem from numerous archives. I finally found a good one at: http://www.apache.org/dist/xml/xerces-c/ -Eric. > -Original Message- > From: Joanne Bogart [mailto:[EMAIL PROTECTED] > Sent: Friday, February 20, 2004 6:43 PM > To: [EMAIL PROTECTED] > Subject:

Re: corrupt archive

I downloaded it, unpacked it, built it, no problem. Sorry I don't remember which site I got it from. The file I got was called xerces-c-current.tar.gz. It didn't have 2_5_0 in the name, but when unpacked the top directory was xerces-c-src_2_5_0 Joanne Bor

Re: corrupt archive

BTW one of the two mirrors I used is ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.apache.org/dist/xml/xerces-c/source/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

corrupt archive

Hi, Is it possible, that the tar.gz archive of the xercesc-2.5.0 source release is corrupt ? I've downloaded them from two different mirrors, and none of them worked. tar complains, that the is not a valid tar archive, though it could extract exactly on file this is the md5sum which I get from

xcercesc 2.3 threading issues

Title: xcercesc 2.3 threading issues Hi, I seem to have threading issues with xercesc 2.3 on solaris 2.8.  Any thoughts?  Typically I'll see crashes that look like: #0  0xfe441c98 in _smalloc () from /usr/lib/libc.so.1 (gdb) where #0  0xfe441c98 in _smalloc () from /usr/lib/libc.so.1 #1  0x

pkg-config

Hi, does someone know if it is planned to support pkg-config? pkg-config is a library management system which is distribution (rpm,deb) independant. Instead every pkg-config compatible application must store a .pc file with library version, dependencies in a central directory. It is used by a grow

Xerces on VMS

I'm running Xerces 2.2.0 (from HP's VMS freeware site) on OpenVMS 7.3, using C++ V6.3-020. I can create an instance of the XercesDOMParser, manipulate it, (parse, get documents, find nodes, add them, etc) delete it, rinse, repeat, etc, as often as I want, as long as there's only one instance at a

RE: Stopping the SAX parser?

How about a combination of SAXParser::error(..., ErrType_Fatal, ...) and SAXParser::setExitOnFirstFatalError(true)? Adam Heinz Senior Software Developer Exstream Software - To unsubscribe, e-mail: [EMAIL PROTECTED] For additiona

Stopping the SAX parser?

Is there any way, from within a DocumentHandler, to indicate to the SAX parser that I don't want parsing to continue? I know I could throw an exception, but I'd prefer to avoid that if possible. Sean - To unsubscribe, e-mail:

DO NOT REPLY [Bug 27119] - Improper handling of elements in external entities

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

DO NOT REPLY [Bug 27119] - Improper handling of elements in external entities

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

DO NOT REPLY [Bug 27119] - Improper handling of elements in external entities

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

DO NOT REPLY [Bug 27119] - Improper handling of elements in external entities

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

DO NOT REPLY [Bug 27119] - Improper handling of elements in external entities

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

DO NOT REPLY [Bug 27119] New: - Improper handling of elements in external entities

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

DO NOT REPLY [Bug 27094] - Graphs are all corrupt in online 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: Annotations

Hi Endre, You don't need to downcast. DOMNode::getNodeName() will return the target, and DOMNode::getNodeValue() will return the data. If you want to downcast, you can just use a static cast, after you've called DOMNode::getNodeType() and verified it's a processing instruction. Dave

DO NOT REPLY [Bug 27094] - Graphs are all corrupt in online 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

Xerces2.5.0 documentation update

Hi, there, The Xerces-c website has been refreshed with 2.5.0 documentation available. Regards, Peiyong Zhang XML Parsers Development, IBM Toronto Laboratory D2-265, 8200 Warden Ave, Markham, Ont L6G 1C7, Canada Email: [EMAIL PROTECTED] Phone: (905)413-4088 Fax: (905)413-4854; T/L: 778

DO NOT REPLY [Bug 27115] - External subset problem with icc 8.0 on IA-64 Linux

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

DO NOT REPLY [Bug 27115] New: - External subset problem with icc 8.0 on IA-64 Linux

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

DO NOT REPLY [Bug 27094] - Graphs are all corrupt in online 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: Annotations

Based on http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1950641 247, I think you've got it right. However, if you want to use the node name and value directly, you'll first need to check the node type as Hiran suggested, just as you would before statically casting it. If your

RE: Annotations

Hi, Endre. I'd use node->getNodeType()==DOMNode::PROCESSING_INSTRUCTION_NODE to decide and then statically cast it, as I am not familiar to VC++ and RTTI. Hiran > -Original Message- > From: Endre Magyari [mailto:[EMAIL PROTECTED] > Sent: Friday, February 20, 2004 3:00 PM > To: [EMAIL P

Re: Annotations

Thanks all, so getTarget() gives "udm" and getData() gives ' name1="value1" name2="value2"' The name of such a node is also "udm" ? And it's value is the data, unparsed? If not, and if I need the class DOMProcessingInstruction to access the information, how do I downcast a DomNode to D

RE: Annotations

A processing instruction doesn't have any structure (such as attributes and other children); its contents are basically just text to be interpreted by the XML processor (hence the name). You can get the target (in this case, the string "udm") with getTarget(), and the remainder of the text in the P

RE: Annotations

Hi, Endre. Have a look at the API documentation: http://xml.apache.org/xerces-c/apiDocs/classDOMProcessingInstruction.html Basically a PI only has a name and data. In your case the name is "udf", and your application has to care about the data (could mean: do further parsing yourself). Hiran >

Re: Annotations

That's a processing instruction named "udm"; to retrieve it, do [...] Thanks ! so it is a node, not an element then. I know how to access the attributes of an Element. How can I access the attributes of a such a Node ? Thanks, Endre

Re: Annotations

At 13.43 20/02/2004 +0200, Endre Magyari wrote: Dear List, Suppose I have parsed in an InputSource with the following code: InputSource *is; DOMParser parser; parser.setValidationScheme(DOMParser::Val_Never); parser.parse(*i

Re: Annotations

Yes, this is a Processing Instruction node, and the DOM offers you the possibility to access PI-Nodes and their data. If they come before the first element node, they will be children of the Document node, and you may access them via the DOM from there. Check the XML Specification for more informa

Annotations

Dear List, Suppose I have parsed in an InputSource with the following code: InputSource *is; DOMParser parser; parser.setValidationScheme(DOMParser::Val_Never); parser.parse(*is); H

Re: BinInputStream question

Thanks. That solved. I know - it was a stupid question. Endre. On Fri, 20 Feb 2004 10:57:57 +0100 (CET), Jeroen N. Witmond <[EMAIL PROTECTED]> wrote: Do you #include ? Dear List, I'm using xerces-c and in my Custom Entity resolver I need to have a look on the resolved entities, for this, I h

Re: BinInputStream question

Do you #include ? > Dear List, > > I'm using xerces-c and in my Custom Entity resolver I need to have a look > on the resolved entities, for this, I have created a functions which > investigates the inputsource: > > I'd like to have a code like this: > > bool CheckForVersionInfo(

BinInputStream question

Dear List, I'm using xerces-c and in my Custom Entity resolver I need to have a look on the resolved entities, for this, I have created a functions which investigates the inputsource: I'd like to have a code like this: bool CheckForVersionInfo(const InputSource* is) {