[Res] Not being able to import WSDL's in SoapUI Pro 4.6.4

We didn't see any problems with imports generally, but the WSDL import code has been changed, and your problem must be related to these changes. Could you please open a support ticket here right away, and we will try to fix the problem as soon as possible: http://www.soapui.org/Support/support-overview.html

EDIT: Please add the ticket number here, so I can find it and start working on it right away.

Kind regards,
Manne

I should add that this may not be a bug, but that SoapUI tries to be more correct in the new version. An educated guess is that you have WSDLs without an XML declaration with encoding specified, and that SoapUI therefore interprets your WSDL as UTF-8 while 4.6.3 used the default encoding.

Whether it's a bug or not, we will try to help you as soon as possible, of course.

/Manne

The support guys came with a solution after i logged a ticket:

1) Open with a text editor the "soapUI-Pro-4.6.4.vmoptions" file located in the "bin" directory of the SoapUI Pro application
2) Add this line at the end of the file:
-Dfile.encoding=UTF8
3) Save the file and restart SoapUI Pro
Try again to load the WSDL in SoapUI Pro 4.6.4.


And it worked, thank you very much!

Hi,

we have a similar problem:
"Error loading [http://...?wsdl]: org.apache.xmlbeans.XmlException: java.io.CharConversionException: Malformed UTF-8 character: 0xdf 0x6"

And we also can avoid this error by changing the vmoptions file.
But I don't think the reason for the error is a missing encoding statement within the wsdl/xds files.
All files I checked do have this statement:
<?xml version="1.0" encoding="UTF-8"?>

So is this a bug, or isn't it?

Best regards
Nico

Hi,

It's hard to say what else could be involved in your particular case, but I would not consider it a bug that in your case the files have the encoding defined. There are likely other changes besides the encoding being taken into account differently when loading WSDLs in the latest SoapUI Pro 4.6.4.

Regards,

Giscard
SmartBear Support

I believe this is a bug in soapui 4.6.4.

The code change although relatively small caused the change in behavior. The load(url) returned a ByteArrayInputStream used to create the XmlObject. Now the code gets the ByteArrayInputStream converts it to a String, does some magical stuff to fix the issue relating to the code change, converts the string back to bytes[], and then the bytes[] is used to create a "new" ByteArrayInputStream that is used to create the XmlObject.

The problem is converting this down to a String and then back to bytes[]. In the process the original wsdl's encoding and charset is lost since String getBytes() will convert based on the jvms file.encoding setting.

The fix would be to preserve the encoding of the original wsdl and use this in getBytes(Charset charset) instead of getBytes().

Hi Hazem,

Please try the SoapUI Pro 4.6.4 maintenance build here:
http://www.soapui.org/Downloads/soapui-pro-nightly-builds.html
And confirm if you still have issues.

Thanks,

Giscard
SmartBear Support

Thanks for the quick reply.

We just tested using the link provided and the same issues exists.

Hi Hazem,

Since this thread is resolved, please reproduce the issue you are having and open a support case with the issue's description and include your error log files from the 'bin' directory of the SoapUI Pro installation. Also mention that you are using the version 4.6.4 maintenance build:
http://www.soapui.org/Support/support-overview.html

Thanks,

Giscard
SmartBear Support

Support case was opened yesterday, SB Case#00028772.

Can you add the notes, retested with Maintenance Build and the problem still exists?