There's a known issue with 2.5 whereby you can't "explicitly" declare xsi:type's in the soap result. This results in the platform not recognizing any xml elements, and, as you are experiencing, nothing being mapped.
The current (nasty) workaround is to change your webservice to not declare the types explicitly in the xml. Ie:
<Slope>0</Slope>
instead of
<Slope xsi:type="xsd:int">0</Slope>
The wsdl has already declared that this element is of type xsd:int, so the information you're sending is superfluous anyway.
update: This will be fixed in 2.5 final. In the meantime, as I suggested, you can try (if possible) to edit the webservice response to not explicitly declare the types. This should fix the bug.
Thanks for your quick response. If you need more info, just let me know.
http://dl.dropbox.com/u/5049895/mendix-forum/call-webservice.png http://dl.dropbox.com/u/5049895/mendix-forum/domain-model.png http://dl.dropbox.com/u/5049895/mendix-forum/input.xml http://dl.dropbox.com/u/5049895/mendix-forum/result.xml http://dl.dropbox.com/u/5049895/mendix-forum/wsdl.xml http://dl.dropbox.com/u/5049895/mendix-forum/xml-to-domain-mapping.png
By the way, setting the debug level of Webservices and Data_synchronization (or something like that) to TRACE provides very useful feedback about the data mapping which is processed. (You can find it under the rocket icon in the console tab)
After 2 webservices log entries (Created soap envelope and called [..] and received response), I get a lot of entries from ConnectionBus_Sync: Available mapping, Added to xmlpath and Endelement encountered. This data seems to be ok. 'Endelement encountered for with content (localName: Envelope)' is the very last message in the console. After that, nothing happens...