[xsd-users] Memory requirements of the C++/Tree in-memory representation

[Boris Kolpackov]

Hi Marco,

Marco Fischer <marco.fischer at chipvision.com> writes:


> Fine, that's basically what I expected. I was a bit unsure, because I
> thought there might be DOM nodes (or maybe other bookkeeping data)
> associated with every instance of a C++/Tree generated class at
> run-time.

By default, after parsing is complete, the DOM document is released.
You can keep the DOM document around (with associations between
C++/Tree and DOM nodes) by passing the xml_schema::flags::keep_dom
flag to one of the parsing functions.


> Does the xsd run-time use DOM nodes when XML is de-serialized and
> discard them after instances of the generated classes are built? Or does
> it use a SAX like parsing process where the instances of generated
> classes are created directly?

It uses DOM during parsing and serialization.


hth,
-boris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 652 bytes
Desc: Digital signature
Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20070105/7855e813/attachment.pgp