When deploying the SU at the first time, its WSDL is updated with the endpoint name.
This update used the WSDLUtil.convertDescriptionToString(...) to get the String associated to the WSDL. Next this WSDL as String is converted into an InputStream to be saved on the local filesystem. So the encoding is not taking into account when writing the WSDL file.
The updated WSDL, as Description, can be directly saved using WSDLUtil.convertDescriptionToFile(...)
When deploying the SU at the first time, its WSDL is updated with the endpoint name.
This update used the WSDLUtil.convertDescriptionToString(...) to get the String associated to the WSDL. Next this WSDL as String is converted into an InputStream to be saved on the local filesystem. So the encoding is not taking into account when writing the WSDL file.
The updated WSDL, as Description, can be directly saved using WSDLUtil.convertDescriptionToFile(...)