[
https://jira.jboss.org/jira/browse/JBESB-3299?page=com.atlassian.jira.plu...
]
Uday updated JBESB-3299:
------------------------
JBoss Forum Reference: (was:
http://community.jboss.org/thread/149527)
Description:
When Proxing a webservice that has special characters in the URL SOAPProxy breaks.
was:
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.
SOAPProxy breaks when WSDL elements have special characters
-----------------------------------------------------------
Key: JBESB-3299
URL:
https://jira.jboss.org/jira/browse/JBESB-3299
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.8
Reporter: Uday
Assignee: David Ward
Fix For: 4.9
Attachments: MyFinan.xml
When Proxing a webservice that has special characters in the URL SOAPProxy breaks.
--
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