Hi Bjori (is that your name by the way?),
I agree with you that introducing the ModelReflection stuff is rather ugly. I didn't like it myself. 

Actually there is a confusion/complication. The thing you need to pass to saveDataObjectToString is the name of the document element name not its __type__. So for example you might pass "company" and get xml with <company>...</company>. The docs were at best amiguous and the example in them was just plain wrong (although now fixed on the livedocs version). What you are going to get back from getType is the type e.g. "CompanyType". I expect it worked for you because your type name and element name were the same? 

We know we need to have an overhaul of the user interface for the XML DAS but have not worked out what to do yet. We will try to incorporate your suggestion that saveDataObjectToString should just do the right thing.

Hi Matthew,
 sorry for leaving out signature - my name is Hannes :)

My type and element names where the same, in this case, yes.
I've been wondering alot about strange results from saveDataObjectToString() from time to time, now I know why, hehe.

The docs are/were quite confusing on how to call saveDataObjectToString correctly - without having to manually type in "shitload" of info ;)

How about doing something like ext/dom does, DOMDocument->saveXML(), for instance, spits out the whole document, by default, but you can ask it to treat specific element as root?

Thanks for the response
- Hannes :)

Hi Hennes, it's been along time coming but we recently put out our 0.9.0 release. Along with some rearrangement of the API for the working with XML, which might hurt a bit (sorry, but we felt it was needed), we did bring back the functionality we had with getType(), although it is now two separate calls, getTypeName() and getTypeNamespaceURI().

And we no longer have saveDataObjectToString() exactly as we used to have it; we now require that you have to have a document to contain it. If you want to serialise a data object you need to have it in a document object and write that out with saveString. If you want to suppress the XML declaration that you would normally get with a document then you can call setXMLDeclaration(false) first.

High five for saveString()!
Works like a charm and exactly what I was hoping for :)