Forum Discussion
omatzura
17 years agoSuper Contributor
Hi,
thanks.. ok.. I tracked this down, it's a bug related to internal SOAP Version handling and will occur when you import a WSDL that only contains a SOAP 1.2 binding (even if you do create a project file). You need to save / reload the project to get it initialized correctly.. either by restarting soapUI or just closing/opening it in the workspace (from the project popup menu, select "Close Project" and then "Open")
Sorry for the inconvenience.. we'll have this fixed in the upcoming snapshot..
and thanks for reporting!
regards,
/Ole
eviware.com
thanks.. ok.. I tracked this down, it's a bug related to internal SOAP Version handling and will occur when you import a WSDL that only contains a SOAP 1.2 binding (even if you do create a project file). You need to save / reload the project to get it initialized correctly.. either by restarting soapUI or just closing/opening it in the workspace (from the project popup menu, select "Close Project" and then "Open")
Sorry for the inconvenience.. we'll have this fixed in the upcoming snapshot..
and thanks for reporting!
regards,
/Ole
eviware.com