Document Generation

You are looking at an older version of the documentation. The latest version is found here.

Document generation starts with the root mapping class and proceeds iteratively and hierarchically over all child mapping classes. This can result in a large number of query executions. For example, if a document has a root mapping class with three child mapping classes. Then for each row selected by the root mapping class after applying the root context criteria, each of the child mapping class queries will also be executed.

Document Correctness

By default, XML generated by XML documents is not checked for correctness against the relevant schema. It is possible that the mapping class queries and the usage of specific SELECT or WHERE clause values will generate a document that is not valid for the schema. See the Document Validation section below on how to ensure correctness.

Sibling or cousin elements defined by the same mapping class that do not have a common parent in that mapping class will be treated as independent mapping classes during planning and execution. This allows for a more document-centric approach to applying criteria and ORDER BY clauses to mapping classes.

Document Validation

The execution property XMLValidation should be set to TRUE to indicate that generated documents should be checked for correctness. Please note that correctness checking will not prevent invalid documents from being generated since correctness is checked after generation and not during it.