Forum Discussion
hazem_borham
11 years agoOccasional Contributor
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().
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().
Related Content
- 8 years ago
- 4 years ago
- 9 years ago
- 8 years ago
Recent Discussions
- 6 days ago
- 10 days ago