RE: string comparisons in xerces

You'll have to get the attributes, iterate through them, and compare the names using XMLString::compareIString(). There is no way to make the Xerces DOM treat names in a case-insensitive manner -- it's contrary to the fundamental design of XML. Dave

RE: string comparisons in xerces

Dave, The problem is when I invoke an xerces lib fn like getAttribute("xyz"). This function internally uses the XMLString::compareString to verify if an attribute with the name "xyz" is present (case sensitive).. I wanted to know if there was a way of instructing the xerces functions to interna

Re: string comparisons in xerces

How about using XMLString::compareIString()? Dave <[EMAIL PROTECTED]

string comparisons in xerces

This is a simple question. Asking as I cannot access the xerces mailing list archives. The XMLString::compareString fn performs case sensitive compares. So, for eg., if the xml has an attribute named "Attrib" and I invoke the getAttribute fn with a param of "attrib", then the fn will fail. What

DO NOT REPLY [Bug 18341] - Cyclic import doesn't correctly handle type restrictions

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 18341] - Cyclic import doesn't correctly handle type restrictions

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 18341] - Cyclic import doesn't correctly handle type restrictions

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 18341] - Cyclic import doesn't correctly handle type restrictions

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 18341] - Cyclic import doesn't correctly handle type restrictions

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 18341] - Cyclic import doesn't correctly handle type restrictions

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 18341] New: - Cyclic import doesn't correctly handle type restrictions

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: help me get rid of some compile errors...

The following code snippet should work: #include using namespace xercesc; int foo() { DOMNode *anode; if (anode->getNodeType()==DOMNode::ELEMENT_NODE) { DOMElement *elem= (DOMElement *)anode; } else { // Oh dear } } This tatic has worked for me in the past

Re: help me get rid of some compile errors...

The following code snippet should work: #include using namespace xercesc; int foo() { DOMNode *anode; if (anode->getNodeType()==DOMNode::ELEMENT_NODE) { DOMElement *elem= (DOMElement *)anode; } else { // Oh dear } } This tatic has worked for me in the past

RE: help me get rid of some compile errors...

Sorry about the inclusion of any unrelated email. I have no clues how that happened. As I mentioned in my email, I have my header files in place. Looks like some header with a "using" clause in it that is causing this problem.. I am beginning to believe it is probably one of our (non xerces) h

Re: help me get rid of some compile errors...

> I am wasting way too much time integrating my app with the > xerces parser. To add to my woes, I am facing compiler different > compiler errors for different projects that use the same xerces > code... :-) Can someone help me fix these errors the easy way ? Was it really necessary to include

help me get rid of some compile errors...

I am wasting way too much time integrating my app with the xerces parser. To add to my woes, I am facing compiler different compiler errors for different projects that use the same xerces code... :-) Can someone help me fix these errors the easy way ? I am trying.. DOMNode *n // it is a valid d

Re: Problem with accentuated letters

Hi Andrei, > for(XMLSize_t i = 0; i < laListe->getLength(); i++) > { >noeud_courant = laListe->item(i); >//on ne peut pas utiliser tempStr car la taille du contenu peur > être superieur à 99 >char * une_fuite_de_memoire_colmate = > XMLString::transcode(noeud_courant->ge

Re: Problem with accentuated letters

Neil Graham wrote: Hi Andrei, Curiously, when I use Xerces DOMParser for parse a XML file, I can save it or print it with DOMWriter, the accentuated characters are quite present but if I reach the nodes, I don't have any more accents. Good; so the parser is evidently doing the right thing.

Re: Problem with accentuated letters

Hi Andrei, Sorry for the misspelling; all the talk about French put me in French mode. :) > I tried: > XMLPlatformUtils::Initialize("fr_FR"); > as that is indicated in a post of this list but the result is the same one. Of course it is; there aren't any French error messages. :) > Curiously,

Re: Problem with accentuated letters

Neil Graham wrote: Hi Andre, Sorry, but it is Andrei XMLPlatformUtils::Initialize("iso8859-1"); XMLPlatformUtils::Initialize("iso-8859-1"); XMLPlatformUtils::Initialize("ISO-8859-1"); XMLPlatformUtils::Initialize("fr_FR"); The first parameter to Initialize represents the Locale (i.e., langu

Re: Problem with accentuated letters

Hi Andre, > XMLPlatformUtils::Initialize("iso8859-1"); > XMLPlatformUtils::Initialize("iso-8859-1"); > XMLPlatformUtils::Initialize("ISO-8859-1"); > XMLPlatformUtils::Initialize("fr_FR"); The first parameter to Initialize represents the Locale (i.e., language) in which parser error messages shoul

Problem with accentuated letters

Hi, Like many people, I have a problem with Xerces-c and iso-8859-1 encoding of XML files. When I parse (I tries XercesDOMParser and DOMBuilder) a XML file containing the (french) accentuated characters, the content of the associated XML node is empty ... When I create a XML text node with accentua

DO NOT REPLY [Bug 18308] - solaris 8.0

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

solaris 8.0

Forwarded message: I would like to know , can I use xerces C++ for Solaris 8.0 with GNU C++ compiler. If yes then which version of xerces is stable. Also I would like to know compatible xalan version. Early response to this will be a great help to me. Thanking you in advance Best Regards, Pa

DO NOT REPLY [Bug 18308] New: - solaris 8.0

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: Validating DOM

Hey Kiran, If you are just interested in validating simple types then this is possible. Form the schema grammar you can do something like: DatatypeValidatorFactory *dtvf = _schemaGrammar->getDatatypeRegistry(); then you can look DatatypeValidators up by: DatatypeValidator *dtv

Re: parsing DOM tree: How to get attribute values ( I don ╢t like mondays)

"Andreas B. Thun" wrote: > > >XMLCh* attrName = XMLString::transcode(attributeName); > >attrVal = nodeElement->getAttribute(attrName); > >delete [] attrName; XMLString::release(&attrName); Would it be better ? > > Yep. Now it╢s perfect. > > ---

RE: Validating DOM

Xerces validates the document while parsing. So it does by default the thing you ask for. But if you need more validation then can be described in a schema then you might try this. Parse the file with SAX. The internal validator validates each element against the schema before calling the SAX even