osdir.com
mailing list archive

Subject: How to use DOMDocumentTraversal - msg#00034

List: text.xml.xerces-c.user

Date: Prev Next Index Thread: Prev Next Index
Hi,

In looking through the Xerces documentation, I could not find any documentation covering the use of DOMDocumentTraversal class. The samples seem to use the DOM API directly and not the Traversal API. The Xerces website claims that Xerces supports DOM Level 2 Traversal and provides a link to the spec, so I imagine that it's just a matter of how to use this API and not whether or not this feature is implemented in Xerces.

Any help would be greatly appreciated.

Thanks,

Erik.



Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

serialization of floating point numbers

Dear XercesC Users, I've the following problem. I'm developing a set of classes to serialize metadata as xml attributes that represents spatial information, something that I should guarantee to be precise from the order of metres to micron. Imagine that I'm using double precision floating points. How the precision is handled by XercesC? Is this done transparently by the user? Is there some documentation regarding this issue? Second question comes now. Is there a way to configure XercesC to serialize floating point numbers with a fixed decimal precision? Is there the way to format the serialization string via the API? Thanks in advance for your help! Ciao Alessandro -- _______________________________________________ Ing. Alessandro Chiarini Technical Manager BioComputing Competence Centre SCS s.r.l. Via Magnanelli 6/3, 40033 Casalecchio di Reno BO, Italy http://tinyurl.com/z24zv tel: +39-051-6171342 mailto:a.chiarini@xxxxxxxxxxxxxx _______________________________________________ The information transmitted is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

Next Message by Date: click to view message preview

What do these SAX2 features exactly mean?

*I am writing a schema validation tool to make the content of a XML file is consistent with a XSD file. Although I can make it work, but I still don't know what the following SAX2 features exactly mean. I can't understand the simple explanation in **http://xerces.apache.org/xerces-c/program-sax2.html*<http://xerces.apache.org/xerces-c/program-sax2.html> *.* ** *Can anybody tell me what they eactly mean, and when I should set them to true (or false)? * ** *1. XMLUni::fgSAX2CoreNameSpaces* *Predefined Constant: * *fgSAX2CoreNameSpaces * *note: * *If the validation feature is set to true, then the document must contain a grammar that supports the use of namespaces. * * * *But what is a grammar that supports the use of namespaces?* *2.XMLUni::fgXercesSchema* *http://apache.org/xml/features/validation/schema * *true: * *Enable the parser's schema support. * *false: * *Disable the parser's schema support. * *What does it mean by "a parser that supports schema"?* *3.XMLUni::fgSAX2CoreNameSpacePrefixes* *http://xml.org/sax/features/namespace-prefixes * *true: * *Report the original prefixed names and attributes used for Namespace declarations. * *false: * *Do not report attributes used for Namespace declarations, and optionally do not report original prefixed names. * *Can anybody give me an example for this?* ** ** *4.XMLUni::fgXercesSchemaFullChecking * *http://apache.org/xml/features/validation/schema-full-checking * *true: * *Enable full schema constraint checking, including checking which may be time-consuming or memory intensive. Currently, particle unique attribution constraint checking and particle derivation restriction checking are controlled by this option. * *false: * *Disable full schema constraint checking. * *default: * *false * *XMLUni Predefined Constant: * *fgXercesSchemaFullChecking * *note: * *This feature checks the schema grammar itself for additional errors that are time-consuming or memory intensive. It does not affect the level of checking performed on document instances that use schema grammars. * *see: * *http://apache.org/xml/features/validation/schema*<http://xerces.apache.org/xerces-c/program-sax2.html#schema> * * *This feature is only used to check grammar in the XSD file?* ** *5.XMLUni::fgXercesDynamic* *http://apache.org/xml/features/validation/dynamic * *true: * *The parser will validate the document only if a grammar is specified. ( http://xml.org/sax/features/validation must be true). * *false: * *Validation is determined by the state of the http://xml.org/sax/features/validationfeature. * *default: * *false * *XMLUni Predefined Constant: * *fgXercesDynamic * *see: * *http://xml.org/sax/features/validation*<http://xerces.apache.org/xerces-c/program-sax2.html#validation> * * The "true" and "false" clauses seems say the same thing?

Previous Message by Thread: click to view message preview

serialization of floating point numbers

Dear XercesC Users, I've the following problem. I'm developing a set of classes to serialize metadata as xml attributes that represents spatial information, something that I should guarantee to be precise from the order of metres to micron. Imagine that I'm using double precision floating points. How the precision is handled by XercesC? Is this done transparently by the user? Is there some documentation regarding this issue? Second question comes now. Is there a way to configure XercesC to serialize floating point numbers with a fixed decimal precision? Is there the way to format the serialization string via the API? Thanks in advance for your help! Ciao Alessandro -- _______________________________________________ Ing. Alessandro Chiarini Technical Manager BioComputing Competence Centre SCS s.r.l. Via Magnanelli 6/3, 40033 Casalecchio di Reno BO, Italy http://tinyurl.com/z24zv tel: +39-051-6171342 mailto:a.chiarini@xxxxxxxxxxxxxx _______________________________________________ The information transmitted is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

Next Message by Thread: click to view message preview

Whitespace DomNode->hasAttributes()

Hi, I`ve created a DomNodeBuilder. Now I`m trying to get the Nodes Attributes via the Method "hasAttributes()" from a DomNode. The difficulty is, that among the content, I also receive whitespace. What is the best method to receive only existing content without other not needed stuff? With best Regards Dennis
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by