The QAbstractXmlNodeModel class is an abstract base class for modeling non-XML data to look like XML for QXmlQuery. More...
Public Typedefs | |
| typedef QList< Ptr > | List |
| typedef QExplicitlySharedDataPointer< QAbstractXmlNodeModel > | Ptr |
Public Types | |
| enum | SimpleAxis |
Public Methods inherited from Protected Methods | |
| virtual QVector< QXmlNodeModelIndex > | attributes (const QXmlNodeModelIndex &element) const = 0 |
| QXmlNodeModelIndex | createIndex (qint64 data) const |
| QXmlNodeModelIndex | createIndex (qint64 data, qint64 additionalData) const |
| QXmlNodeModelIndex | createIndex (void *pointer, qint64 additionalData=0) const |
| virtual QXmlNodeModelIndex | nextFromSimpleAxis (SimpleAxis axis, const QXmlNodeModelIndex &origin) const = 0 |
Detailed Description
The QAbstractXmlNodeModel class is an abstract base class for modeling non-XML data to look like XML for QXmlQuery. The QAbstractXmlNodeModel specifies the interface that a node model must implement for that node model be accessible to the query engine for processing XQuery queries. A node model represents data as a structure that can be queried as if the data were XML.
The node model represented by a subclass of QAbstractXmlNodeModel is meant to be accessed by the CsXmlPatterns query engine. If the API seems a little strange in a few places, it is because the member functions are called by the query engine as it evaluates an XQuery. They are not meant to be used programmatically.
Usage
QAbstractXmlNodeModel bridges the gap between the arbitrary structure of the non-XML data to be queried and the well-defined structure of XML data understood by QXmlQuery.
Consider a chemistry application that reads the file chemistryData, which contains non-XML data that represents a chemical structure composed of molecules and atoms. The application will query this chemistry data with an XQuery it reads from file queryFile. We write a custom subclass of QAbstractXmlNodeModel (ChemistryNodeModel) that reads chemistryData and builds a data structure, perhaps composed of objects of our own classes molecule and atom. Clearly, this data structure is not XML. Our custom subclass will know how to traverse this non-XML structure and present it through the XPath Data Model interface.
The application first creates an instance of QXmlQuery and calls setQuery() to read queryFile containing the XQuery we want to run. Then it creates an instance of our custom node model class, ChemistryNodeModel, which is a subclass of QAbstractXmlNodeModel. Its constructor is called with the name pool obtained from our QXmlQuery, and with the chemistryFile containing the structure of molecules and atoms to be queried. The name pool is required because our custom node model has the member function name(), which returns the name of any node in the model. The query and the custom node model must use the same name pool for constructing these names. The constructor would then read chemistryFile and build the custom node model structure.
To connect the query to the custom node model, we must bind a variable name used in the query to a node in the model. The variable can then be used in the query as a starting node. First, an index for the desired starting node is retrieved by calling QAbstractXmlNodeModel::createIndex(). Then the index is bound to a variable name, in this case queryRoot, by passing the name and the index to QXmlQuery::bindVariable(). The query can then use a variable reference $queryRoot to refer to the starting node. Note that if the query uses multiple variable references, a call to QXmlQuery::bindVariable() is required to bind each different variable name to a node in the model.
The query is executed when the application calls one of the QXmlQuery evaluation functions. The application uses QXmlQuery::evaluateTo(QAbstractXmlReceiver *), because it then uses a serializer to out the query result as XML to stdout. We could have used QXmlQuery::evaluateTo(QXmlResultItems *) to get a list of result items, or QXmlQuery::evaluateTo(QStringList *) if the query evaluated to a sequence of xs:string values.
During query execution, the engine iterates over the node model using nextFromSimpleAxis() to get the index of the next node to be visited. The engine can get the name of a node by calling name() with the node's index. stringValue(), baseUri(), documentUri() and kind() are also called as needed with a node index.
The example demonstrates the standard pattern for using a subclass of QAbstractXmlNodeModel in combination with QXmlQuery to perform an XQuery.
- Instantiate QXmlQuery and give it the XQuery to be run;
- Instantiate a subclass of QAbstractXmlNodeModel or QSimpleXmlNodeModel;
- Retrieve a QXmlNodeModelIndex for the node in the model where the QXmlQuery should start the query;
-
Use QXmlQuery::bindVariable() to bind the QXmlNodeModelIndex to
$variable name; - Call one of the QXmlQuery evaluation functions to run the query.
Subclassing
Because the XPath Data Model interface presented by QAbstractXmlNodeModel allows QXmlQuery to operate on non-XML data as if it were XML, implementing subclasses of QAbstractXmlNodeModel can involve a significant amount of work. The QSimpleXmlNodeModel class is provided to simplify the implementation for many common use cases.
Thread Safety
Because the node model can be accessed concurrently by threads in the CsXmlPatterns library, subclasses of QAbstractXmlNodeModel must be written to be conditionally thread safe. Classes QReadLocker and QWriteLocker can be used to make your derived class thread-safe.
- See also
- QExplicitlySharedDataPointer
Member Typedef Documentation
A list of smart pointers to instances of QAbstractXmlNodeModel.
- See also
- QExplicitlySharedDataPointer
A smart pointer to an instance of QAbstractXmlNodeModel.
- See also
- QExplicitlySharedDataPointer
Member Enumeration Documentation
Four axes that each contain one node only.
| Constant | Value | Description |
|---|---|---|
QAbstractXmlNodeModel::Parent | 0 | The parent of the context node |
QAbstractXmlNodeModel::FirstChild | 1 | The first child of the context node |
QAbstractXmlNodeModel::PreviousSibling | 2 | The previous child of the context node |
QAbstractXmlNodeModel::NextSibling | 3 | The next child of the context node |
Constructor & Destructor Documentation
| QAbstractXmlNodeModel::QAbstractXmlNodeModel | ( | ) |
Default constructor.
|
virtual |
Destructor.
Method Documentation
|
protectedpure virtual |
Returns the attributes of element. The caller guarantees that element is an element in this node model.
|
pure virtual |
Returns the base URI for the node whose index is index. The caller guarantees that index is not null and that it belongs to a node in this node model.
The base URI of a node can be extracted using the fn:base-uri() function. The base URI is typically used for resolving relative URIs that appear in the node or its children. It is conformant to just return the document URI, although that might not properly reflect the underlying data.
This function maps to the dm:base-uri accessor, which returns a base URI according to the following:
- For document nodes, the base URI and the document URI are the same.
-
For elements, the base URI is the URI appearing in the element's
xml:baseattribute, if present, or it is resolved to the parent element's base URI. - Namespace nodes have no base URI.
- The base URI for a processing instruction, comment, attribute, or text node is the base URI of the node's parent element.
The implementation guarantees to return a valid QUrl, or a default constructed QUrl. If a node has no base URI, as in the case where a comment has no parent, a default constructed QUrl is returned.
Implemented in QSimpleXmlNodeModel::baseUri()
|
pure virtual |
This method returns the relative document order for the nodes index1 and index2. It is used for the Is operator and for sorting nodes in document order. The caller guarantees that index1 and index2 are not null and both identify nodes in the current model.
If index1 is identical to index2 then QXmlNodeModelIndex::Is is returned. If index1 precedes index2 in document order, QXmlNodeModelIndex::Precedes is returned. If index1 follows index2 in document order, QXmlNodeModelIndex::Follows is returned.
|
inlineprotected |
Creates a node index with data as its internal data. The value for data is not constrained.
|
inlineprotected |
Creates a QXmlNodeModelIndex containing data and additionalData.
|
inlineprotected |
Creates a node index with pointer and additionalData as its internal data. The values for pointer and additionalData are not constrained.
|
pure virtual |
Returns the document URI of index. The document URI identifies the resource which is the document. For example, the document could be a regular file such as "file:/", or it could be the "http://" URL of the location of a file. The document URI is used for resolving URIs and to simply know where the document is.
If the node model maps to a URI in a natural way, return that URI. Otherwise, return the company or product URI. The document URI can be any URI as long as its valid and absolute.
The caller guarantees that index is not null and that it belongs to this QAbstractXmlNodeModel.
This function maps to the dm:document-uri accessor, which returns a document URI according to the following:
|
pure virtual |
Returns the index of the element identified as id. XQuery's id() method calls this method.
The node index returned will be the element node whose value is of type ID and equals id, or it will be the element node that has an attribute whose typed value is of type ID and equals id. If there is no such element, a default constructed QXmlNodeModelIndex instance is returned. The implementor guarantees that if the returned node index is not null, it identifies an element.
It is not sufficient for an attribute or element to merely be called id. Its value type must also be ID. However, the reserved name xml:id is sufficient.
In id, the namespace URI and the prefix are undefined, and the local name is the ID that should be looked up.
Implemented in QSimpleXmlNodeModel::elementById()
|
pure virtual |
Returns a value indicating the kind of node identified by index. The caller guarantees that index is not null and that it identifies a node in this node model. This method maps to the dm:node-kind() accessor.
|
pure virtual |
Returns the name of index. The caller guarantees that index is not null and that it belongs to this QAbstractXmlNodeModel.
If a node does not have a name, e.g., comment nodes, a null QXmlName is returned. QXmlNames must be created with the instance of QXmlQuery that is being used for evaluating queries using this QAbstractXmlNodeModel.
This function maps to the dm:node-name() accessor.
If index is a processing instruction, a QXmlName is returned with the local name as the target name and the namespace URI and prefix both empty.
|
pure virtual |
Returns the in-scope namespaces of index. The caller guarantees that index is not null and that it belongs to this QAbstractXmlNodeModel.
This function corresponds to the dm:namespace-nodes accessor.
The returned vector of namespace declarations includes namespaces of the ancestors of n.
The caller guarantees that index is an Element that belongs to this QAbstractXmlNodeModel.
Implemented in QSimpleXmlNodeModel::namespaceBindings()
|
protectedpure virtual |
When CsXmlPatterns evaluates path expressions, it emulate them through a combination of calls with QSimpleXmlNodeModel::SimpleAxis values. Therefore, the implementation of this function must return the node, if any, that appears on the axis emanating from the origin.
If no such node is available, a default constructed QXmlNodeModelIndex is returned.
QSimpleXmlNodeModel eliminates the need to handle redundant corner cases by guaranteeing that it will never ask for:
- Children or siblings for attributes.
- Children for comments, processing instructions, and text nodes.
- Siblings or parents for document nodes.
A typical implementation performs a switch on the value of axis.:
|
pure virtual |
Returns the elements and/or attributes that have an IDREF value equal to id. The implementor guarantees the nodes identified by the returned indexes are elements or attributes.
It is not sufficient for an attribute or element to merely be called idref. It must also be of type IDREF. Elements must be typed as xs:IDREF or xs:IDREFS, or, in the case of attributes, as IDREF or IDREFS in the schema.
In id, the namespace URI and the prefix are undefined, and the local name is the ID that should be looked up.
Implemented in QSimpleXmlNodeModel::nodesByIdref()
|
pure virtual |
Returns the root node of the tree that contains the node whose index is index. The caller guarantees that index is not null and that it identifies a node in this node model.
If index identifies a node that is a direct child of the root, parent() would return the same QXmlNodeModelIndex returned by this function.
| QSourceLocation QAbstractXmlNodeModel::sourceLocation | ( | const QXmlNodeModelIndex & | index | ) | const |
Returns the source location for the object with the given index or a default constructed QSourceLocation in case no location information is available.
|
pure virtual |
Returns the string value for node index. The caller guarantees that index is not null and that it belong to this QAbstractXmlNodeModel instance.
This function maps to the dm:string-value() accessor, which the specification completely specifies. Here is a summary:
- For processing instructions, the string value is the data section(excluding any whitespace appearing between the name and the data).
- For text nodes, the string value equals the text node.
- For comments, the content of the comment
- For elements, the concatenation of all text nodes that are descendants. Note, this is not only the children, but the childrens' childrens' text nodes, and so forth.
- For document nodes, the concatenation of all text nodes in the document.
Implemented in QSimpleXmlNodeModel::stringValue()
|
pure virtual |
Returns the typed value for node index. The typed value is an atomic value, which an element or attribute contains.
The caller guarantees that index is either an element or an attribute. The implementor guarantees that the returned QVariant has a value which is supported in XQuery. It can not be an arbitrary QVariant value. The implementor also guarantees that stringValue() returns a lexical representation of typedValue()(this is guaranteed by QSimpleXmlNodeModel::stringValue()).
If the return QVariant is a default constructed variant, it signals that index has no typed value.
- Generated on Wed Sep 25 2024 09:00 by
1.7.0