Bug 779696 (SOA-2060)

Summary: character encoding problem with WSDL contracts
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Kevin Conner <kevin.conner>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 GACC: dlesage
Target Milestone: ---   
Target Release: 5.0.2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2060
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-10 09:41:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Kevin Conner 2010-04-29 15:31:24 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2010-05-01 21:31:34
project_key: SOA

Comment 1 Kevin Conner 2010-04-29 15:31:46 UTC
Link: Added: This issue depends JBESB-3280


Comment 2 David Ward 2010-05-02 01:31:34 UTC
JBESB-3280 has been closed.

Comment 3 David Ward 2010-05-06 16:52:59 UTC
Added "Affects: Documentation" so people know the Programmer's Guide, and thus the SOA-P documentation, needs to be updated along with this.

Comment 4 David Ward 2010-05-06 16:52:59 UTC
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]


Comment 6 David Le Sage 2010-06-16 23:34:11 UTC
Draft text for Release Note states:


https://jira.jboss.org/browse/JBESB-3280

    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.


Comment 7 Boris Belovic 2010-06-28 15:03:40 UTC
Verified in SOA-P 5.0.2 CR3 (covered by WebServiceProxyTest).

Comment 9 trev 2010-09-10 09:40:20 UTC
I think it affects many character sets, not just russian                                
Probably anything that is not UTF-8/ASCII