DO NOT REPLY [Bug 18215] - to get value of node

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 18215] New: - to get value of node

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

How to use cached grammar

I am trying the following piece of code XMLPlatformUtils::Initialize(); SAX2XMLReader* parser = XMLReaderFactory::createXMLReader(); parser->loadGrammar("d:\\datacenter\\xml\\Storeinfo.dtd", Grammar::DTDGrammarType, true); parser->setFeature(XMLUni::fgSAX2CoreNameSpaces, true);

Re: XercesDOMParser::parse() - Is this Recursive?

HI Renin, If you mean "re-entrant" the answer is no -- a single instance of a parser can only parse one document at a time. See: http://xml.apache.org/xerces-c/faq-parse.html#faq-7 Dave

XercesDOMParser::parse() - Is this Recursive?

Hi, I am a newbie at using Xerces C++. I have written a multi-threaded program that uses the XercesDOMParser to parse my xml document. I am wondering if the XercesDOMParser::parse() is recursive? I looked at the source code, and it appears to be non-recursive. But the source code is really compl

Re: Encoding scheme with DOMWriter

Hi Elliot, The last two lines of your code seem to be the most interesting: XMLCh* tempxmltext=theSerializer->writeToString(*m_Node); The documentation of the writeToString method [1] quite clearly states that the output will be in UTF-16 and that the document's encoding will be igno

Encoding scheme with DOMWriter

I am having trouble with the writeToString function of the DOMWriter. Basically, when I load an xml file using XercesDOMParser parse(path), and then print the information using writeToString, the decl shows up with the wrong encoding. The odd thing is that the DOMDocument getEncoding() function i

RE: Internet Access for schema's

Hi Rachael, No, I believe URNs are different from URLs, so "urn:com:company:..." is not relative. Dave "Rachael

RE: Internet Access for schema's

> Actually, relative URI references are officially deprecated > for namespace > declarations: > >http://www.w3.org/XML/xml-names-19990114-errata > > So, I think it's best to avoid them. You're right of course. Namespace declarations are much more useful when they give you an idea of what t

RE: Internet Access for schema's

Hi Rachael, Thanks for your clear, concise explanation. Just one nit to pick: > Note that namespace names (e.g. http://www.w3.org/2001/XMLSchema) are not required to > even *be* urls or be urls that resolve to anything. The namespace declaration > xmlns:foo="Dkdfjsiex8023wndDKsdkS" is a vali

RE: Internet Access for schema's

> Does the following URL in the instance document > in the schema document, require the machine to be > connected to the internet ? No you don't need to be connected to the internet. > If NOT, are these URLs stored locally in the Xerces > utilities ( some string pool ?? ) and get compared > wit

Internet Access for schema's

Hi, Does the following URL in the instance document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance OR http://www.w3.org/2001/XMLSchema"; in the schema document, require the machine to be connected to the internet ? If NOT, are these URLs stored locally in the Xerces utilities ( some

Internet / network access for Xerces parser

Hi, I have following queries - 1. Does Xerces parser require the machine to be on the network / Internet connection. I verified, that in processing of a schema/namespace enabled XML file, the constructor for XMLURL gets called only once ( and the generated URL is a dummy URL and does not get us

DO NOT REPLY [Bug 12436] - UTF-8 transcoder is not strict (and therefore not secure).

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 15389] - Xlat tool does not compile under 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 12436] - UTF-8 transcoder is not strict (and therefore not secure).

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 12436] - UTF-8 transcoder is not strict (and therefore not secure).

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: parsing DOM tree: how can I access two different siblings?

because you are responsible for deleting the memory returned by XMLString::transcode(). Also, these are invariant, so why not move them out of the loop? Hmm, that´s a good hint. But then I would only be able to free the memory at the program´s end, anyway.

Re: parsing DOM tree: how can I access two different siblings?

Hi Andreas, This is a memory leak: if (XMLString::compareString(node->getNodeName(), XMLString::transcode("ConstraintTypes")) == 0) because you are responsible for deleting the memory returned by XMLString::transcode(). Also, these are invariant, so why not move them out of the loop? c

question regarding network (winsock) access with xerces

I am using xerces to get xml from the net. I was wondering if there was any easy way to implementing TIMEOUTS while making url requests ? Looking at the code, I am not sure if this is a trivial job. Right now, I am doing some circus with threads to emulate a timeout. I am working on a soft real

RE: parser->parse() method

no you dont. everything is in place. but depending on your platform, you may need to link with your socket implementation libs. e.g, for windows you may need to link with ws2_32.lib -Vinayak > -Original Message- > From: John Meyer [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 20, 20

parser->parse() method

Hi, If I pass a full URL to parser->parse() is there any other components I need to add in order to let xerces access the web? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Quick question

oh, so that's what that program does. Thanks. -Original Message- From: Vitaly Prapirny [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 12:36 AM To: [EMAIL PROTECTED] Subject: Re: Quick question Do you have Build\Win32\BCB6 and Build\Win32\BCB6\objs directories ? If not then you

porting to Zaurus-Embedix

Hi, Has anyone tried to compile Xerces-c to Embedix, on Zaurus PDA platform (gcc 2.95.3, QTopia Embedix Linux) ? Thanks, Nikko --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.462 / Virus Database: 261 - Release Date: 13/03/2003

Re: parsing DOM tree: how can I access two different siblings?

AccessControlGroups->getNextSibling()->getNextSibling() should return the Type element (not that I'm recommending such unsafe code!). Safety is an issue, So I decided to scan it this (safer?!) way: // Find the XML doc root element DOMDocument *DomDoc = parser->getDocument(); D

Re: parsing DOM tree: how can I access two different siblings?

Or you might want to use the SAX parser. For efficiently extracting whatever content you need from an entire document, it's hard to beat. I find DOM more useful for constructing and modifying documents. I have to use the DOM parser because I hae to build a DOM interface. --

RE: parsing DOM tree: how can I access two different siblings?

Or you might want to use the SAX parser. For efficiently extracting whatever content you need from an entire document, it's hard to beat. I find DOM more useful for constructing and modifying documents. -Original Message- From: Andreas B. Thun [mailto:[EMAIL PROTECTED] Sent: Thursday, Marc

Re: parsing DOM tree: how can I access two different siblings?

> > scan every node -> process only the element and attribute nodes I need > -> use node names to distinguish between the elements. sounds good to me. Gareth -- Gareth Reakes, Head of Product Development +44-1865-203192 DecisionSoft Limitedhttp://www.decisionsoft.com

Re: parsing DOM tree: how can I access two different siblings?

Jesse Pelton schrieb: tags. It would be more robust to check the type of each node you encounter and skip it if you determine that it's text you don't care about. From this I learn that it is better to use the tree walker?! scan every node -> process only the element and attribute nodes I need ->