[esb-issues] [JBoss JIRA] Updated: (JBESB-3279) character encoding problem with WSDL contracts

[David Ward (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Ward updated JBESB-3279:
------------------------------

    Attachment: contract_encoding.zip


I am attaching a quickstart where one can reproduce the issue.  Simply "ant deploy" it to a running ESB server, go to http://localhost:8080/contract/ , then click on the contract JSP wsdl link, and also the HttpGatewayServlet wsdl link.

> character encoding problem with WSDL contracts
> ----------------------------------------------
>
>                 Key: JBESB-3279
>                 URL: https://jira.jboss.org/jira/browse/JBESB-3279
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: 4.8
>            Reporter: David Ward
>            Assignee: David Ward
>             Fix For: 4.9
>
>         Attachments: contract_encoding.zip
>
>
> A user posted an issue where Russian characters are getting marred by the contract JSP application, or WSDL getting chopped by the HttpGatewayServlet.  (Please refer to the JBoss Forum Reference link associated with this issue.)
> In the original WSDL, (ItemService.wsdl), you see Russian characters like this:
> <s:documentation xml:lang="RU">Öåëü:Öåëü</s:documentation>
> If you front the ESB service with a JBR/HTTP gateway, the characters come out like this:
> <s:documentation xml:lang="RU">????:????</s:documentation>
> And if you front the ESB service with the HTTPGatewayServlet, the entire WSDL document gets chopped:
> XML Parsing Error: unclosed token
> Location: http://localhost:8080/contract_encoding/http/Examples/ItemService?wsdl
> Line Number 1558, Column 11:          <s:element minO
> ----------^
> We need to handle the character encoding properly in both cases.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira