Hi
eret1k,
Great youve nailed this down!!! However, the successful loading of the file when you select anonymous auth and the error response generated when you try loading in the .wsdl with NTLM auth is the clue.
The warning is generated by the xmlparser when you load it into soapui. I dont know which parser soapui's using but the soapui developers wouldve just grabbed one that is available...they wouldnt have bothered coding a new parser when theyre freely available so i dont think the issue is with soapui itself.
I think (without knowing more about whats going on), that when you export the .wsdl when creating (and specifying NTLM auth) this creates some additional xml (including the   entity) that is causing the error response. Once the   entity is removed from the .wsdl the issue i think will be resolved.
So i think you have 2 choices. Load in a .wsdl with no auth and then update the auth for each SOAP request and hope the auth is inherited successfully for each test step once the file is successfully loaded into soapui, OR create the .wsdl with the NTLM auth (which should generate the problematic entity 'nbsp') then edit the file to remove the malformed xml.
As i said above, this is a parser error and parsers report only malformed xml errors. If you open the .wsdl in xmlspy it'll show you exactly where the problem is. You can then edit it to remove the malformed bit, thereby making the .wsdl wellformed xml which will then allow you to launch the .wsdl in soapui!
Hope ive explained it clearly,
Nice one!
Rich
Id suggest launching the .wsdl in an app with a parser
