4:04 p.m.
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
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
4:06 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
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
10:38 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3279:
-----------------------------------
This is the reason the WSDL was getting chopped:
http://mark.koli.ch/2009/09/remember-kids-an-http-content-length-is-the-n...
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
4:14 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3279:
-----------------------------------
Please provide feedback on the forum post, per my findings here:
http://community.jboss.org/message/539893#539893
I have made the change locally on my copy of trunk, but obviously have not checked it in
yet. Thank you.
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
4:31 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3279:
------------------------------
Comment: was deleted
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
7:27 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3279:
------------------------------
Comment: was deleted
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
7:31 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-3279.
-----------------------------
Resolution: Done
The fix was to add a property to the SOAPProxy action called "wsdlCharset"
(camel-case to be consistent with wsdlTransform, another supported property). If the user
defines a character encoding with this property, the wsdl will be read in as that charset,
before being transformed and displayed as UTF-8. Our contract JSP application and the
HttpGatewayServlet will always output UTF-8, to be consistent with WS Basic Profile. If
the wsdlCharset property is not defined, the charset returned by the HTTP Content-Type
response header (if the wsdl was loaded via http) will be attempted.
$ svn commit
Sending product/contract-web/src/main/webapp/contract.jsp
Sending product/contract-web/src/main/webapp/index.jsp
Sending product/docs/ProgrammersGuide.odt
Sending product/docs/ProgrammersGuide.pdf
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/gateway/http/HttpGatewayServlet.java
Sending
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/AbstractWsdlContractPublisher.java
Sending
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/RemoteWsdlLoader.java
Sending
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/proxy/SOAPProxy.java
Sending
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/proxy/SOAPProxyWsdlLoader.java
Transmitting file data .........
Committed revision 32701.
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
7:33 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward reopened JBESB-3279:
-------------------------------
Reopening Issue just so I can attach another example quickstart, as well as a screenshot.
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
7:35 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3279:
------------------------------
Attachment: good-russian-wsdl-screenshot.jpg
good-russina-wsdl-screenshot.jpg shows the output of the fix.
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-fix.zip, contract_encoding.zip,
good-russian-wsdl-screenshot.jpg
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
7:35 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-3279.
-----------------------------
Resolution: Done
Re-closing issue now that I've added my 2 new attachments.
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-fix.zip, contract_encoding.zip,
good-russian-wsdl-screenshot.jpg
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
7:35 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3279:
------------------------------
Attachment: contract_encoding-fix.zip
The contract_encoding-fix.zip quickstart builds on the contract_encoding.zip quickstart,
but with the new wsdlCharset property set so it works. Also, there are some other sample
encodings (like KOI8-R and Cp1251) that work as well.
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-fix.zip, contract_encoding.zip,
good-russian-wsdl-screenshot.jpg
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
7:37 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3279:
-----------------------------------
One final note: If you are testing this out yourself, remember you need to install the
proper fonts on your system/browser for the characters to display correctly.
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-fix.zip, contract_encoding.zip,
good-russian-wsdl-screenshot.jpg
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
11:51 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward reopened JBESB-3279:
-------------------------------
Re-opening this issue to add the "Affects" field so I can flag that there was a
documentation change that needs to end up being reflected in the SOA-P documentation.
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-fix.zip, contract_encoding.zip,
good-russian-wsdl-screenshot.jpg
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
11:51 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3279:
------------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.)]
Added "Affects: Documentation"
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-fix.zip, contract_encoding.zip,
good-russian-wsdl-screenshot.jpg
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
11:53 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-3279) character encoding problem with WSDL contracts
[
https://jira.jboss.org/jira/browse/JBESB-3279?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-3279.
-----------------------------
Resolution: Done
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-fix.zip, contract_encoding.zip,
good-russian-wsdl-screenshot.jpg
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
5729
days inactive
5752
days old
14 comments
1 participants
participants (1)
-
David Ward (JIRA)