Thanks for the reply Paul.
Yes , we (both QA & Dev team) agree it is almost certainly not soapUI. That's why I posted in the general forum. Was hoping someone might have insight into why the webservices are building the response according to some lexical ordering instead of following the xsd sequence ...
hopefully something along the lines of 'with the new xyz library that comes with the new Weblogic server you have to configure the foo switch ' or something
As far as we can tell, our webservices code has not changed, nor has our soapUI version or test projects.
