Red Hat Bugzilla – Bug 779696
character encoding problem with WSDL contracts
Last modified: 2010-09-10 05:41:07 EDT
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2010-05-01 21:31:34
Link: Added: This issue depends JBESB-3280
JBESB-3280 has been closed.
Added "Affects: Documentation" so people know the Programmer's Guide, and thus the SOA-P documentation, needs to be updated along with this.
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]
Draft text for Release Note states:
WSDL contracts suffered from a character encoding problem. This occurred when Russian
character sets were used by the Contract JSP application. The WSDL contracts were also being
truncated by the HttpGatewayServlet in this scenario. The software has now been changed to
fully support Russian character encoding. As a result, the Russian alphabet can now be displayed
and WSDL contracts are no longer truncated.
Verified in SOA-P 5.0.2 CR3 (covered by WebServiceProxyTest).
I think it affects many character sets, not just russian
Probably anything that is not UTF-8/ASCII