Characters larger than 4 bytes are not supported: byte 0xae

This is a problem for us also. Simply importing industry standard ws-addr.xsd causes this error. SoapUI chokes on the Unicode copyright symbol 0xa9. Even if this file is in error (doubtful), it is everywhere, and it really needs to be accepted.

I just tried to reproduce this, using a WSDL where I inserted the copyright symbol, but the import went just fine. I also tried importing a WSDL file referencing an XSD with the symbol and didn't get any problems. Could you point me in the direction of a public WSDL that you fail to import?

Kind regards,
Manne, SoapUI developer

Hi,

here is a zip with wsdl & xsd, used in SoapUI 4.6.4.
It is the schema "org\oasis-open\docs\wss\2004\01\oasis-200401-wss-wssecurity-secext-1.0.xsd\oasis-200401-wss-wssecurity-secext-1.0.xsd" that causes the trouble.
I tried to search for the 0xa9 byte, without success ...

Hi,

here is a zip with wsdl and xsd causing the issue.
It works with SoapUi V3.5 & 4.0.1 but not with v4.6.4
The schema file causing the issue is oasis-200401-wss-wssecurity-secext-1.0.xsd (in org\oasis-open\docs\wss\2004\01\oasis-200401-wss-wssecurity-secext-1.0.xsd\ )

I inspected the file in hexadecimal view but did not found the 0xa9 byte.

I just received the "Characters larger than 4 bytes are not supported" error when trying to load the V2 WSDL from the latest version of Magento (1.7) in SOAP UI 4.6.4.

Attempt to load: http://<magentohost>/api/v2_soap?wsdl=1

Message received: Error loading [http://schemas.xmlsoap.org/soap/encoding/]: org.apache.xmlbeans.XmlException: java.io.CharConversionException: Characters larger than 4 bytes are not supported: byte 0xa9 implies a length of more than 4 bytes

This seems a regression in SoapUI 4.6.4 compared to 4.6.3.

This change (Remove property expansions on WSDL and WADL import) has caused the issue
https://github.com/SmartBear/soapui/com ... caa7e6b4a6

Previous code
return XmlUtils.createXmlObject( load( url ), options );

New code

String content = readCleanWsdlFrom( url );
return XmlUtils.createXmlObject( new ByteArrayInputStream( content.getBytes() ), options );
// unnecessary byte[] conversion, XmlUtils has method with string input

readCleanWsdlFrom
Tools.readAll( load( url ), 0 ).toString(); // --> does not respect the encoding of the file

Yeah, I suspected it had something to do with that change.

Thanks for looking into it Richard! We'll try to provide a fix before long.

/Manne

hi, a pull request is available for this issue, see https://github.com/SmartBear/soapui/pull/37