I must be doing something wrong with the parenting of elements, since it seem that only the first element I add to the document is always printed. I’ve tied to remove the processing instruction and then the rolesElement is placed and so on. But I cannot see where the error is….

You’re trying to put multiple elements on the level of the root node.

• Create your processing instruction and add it to the document (like you’re doing already).
• Create a root element and add it to the document

All further elements must be added not to the document, but to the root element (or below). You can retrieve the root element (the one you’ve created previously) via xmlDocument.documentElement().

i.e you’re trying this:

DerManu wrote:

All further elements must be added not to the document, but to the root element (or below). You can retrieve the root element (the one you’ve created previously) via xmlDocument.documentElement().

Uhm..sorry, I still don’t get it. I’ve rewritten the code in order to make it clear what is the root element and I’ve removed the processing instruction since at the moment I don’t need it:

So each child element “currentRoleElement” is actually appended to the root element and the latter to the document. I don’t see where I’m trying to add all elements as root elements of the document.
The hierarchy should be that:

Sorry, it seems I’ve overlooked something in your code, I thought you were adding more than one element directly to the document instead of the root node.

However, this works for me:

it produces as expected

So my guess is there’s something wrong with your “Role” mechanism.

I found a possible problem when creating the text node, that seem to break the tree.
If I do the following:

An other update, that solves my problem but leaves me with a doubt.
The following is the way I was testing the output document, thru which I report the above problems:

and the following is a way that prints out the document into a file that works:

So seems to me that the document is suffering some way of “flushing” when the toString is called?

That sure is a bit strange. I’m not aware of such buffering making toString and save behave differently, and it doesn’t happen when I test it.

What does currentRole.id() typically contain? Invalid tag characters? Numbers only? In this case, the XML becomes invalid, so when your InvalidDataPolicy (see QDomImplementation::setInvalidDataPolicy) is DropInvalidCharacters or ReturnNullNode, you might get an empty XML document. However, this would cause some debug output along the lines of “Calling appendChild() on a null node does nothing.”

DerManu wrote:

T What does currentRole.id() typically contain? Invalid tag characters?

Plain text, no makrup signs (e.g., dev, doc). I’m investigating more to see if I find the cause.

I’ve just looked through the code of qdom.cpp [qt.gitorious.org] and there are no signs of such buffering. Both QDomDocument::save and toString internally call the save functions recursively on the document nodes. In fact, toString just creates a QTextStream on the returned string and writes its content with save itself. So this definetly isn’t the cause.