Are there problems with WS-I compliance checking in soapUI? It appears to be validating log-sample.xml, and ignoring the WSDL I select from the soapUI application, and so giving a false successful report.
After trying to resolve this, I eventually used the tools provided by ws-i from here
and was able to do the required checks. The reports produced from these do look very different to the reports produced from soapUI.
Looking at the temporary data produced by soapUI in C:\Users\..\AppData\Local\Temp, one possible explanation is the temporary WSDLs created there. The WSDLs under test use <import> , but the location of additional files in these imports is relative, and so the imports might not be working.