Who cares what the XML looks like? You import the wsdl and off you go.
IF it works. Which it almost never does (in my experience: 3 fails out of 3 trials), unless you are using the same SOAP library on both ends.
Re:Annoyances of API Design
by eoincathal on Friday January 29, 2016 @07:29AM
(#10994815)
Similar experiences for me. Needed to spend time tweaking a wsdl so it produced the same behaviour in 2 SOAP webservice endpoints, one using dotNET tooling and the other Java. Worked fine after a bit of fiddling but leaves an uneasy feeling.
Huh? How do you know what types <a><b c="d"><e/></b><b f="g" /><a> has? How do you transform that into a Java object? For that matter, if you manage to turn this into a Java object, how do you know how to transform it back into XML? What members turn into attributes and which turn into sub-elements?
Or are you referring to XSD, which showed up years later, is not required, and often not used? Yes, XSD grafts typing onto XML quite effectively, but this is a bolt-on just like the JSON approaches. It just turned out to be a widely-adopted bolt-on.