-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 4.7 CP1
-
Fix Version/s: 4.7 CP2
-
Component/s: Web Services
-
Labels:
-
Forum Reference:
-
Affects:Documentation (Ref Guide, User Guide, etc.)
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.
- blocks
-
SOA-2060 character encoding problem with WSDL contracts
-
- Closed
-
- is related to
-
JBESB-3279 character encoding problem with WSDL contracts
-
- Closed
-