[
https://issues.apache.org/jira/browse/CXF-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552011
]
Benson Margulies commented on CXF-1289:
---------------------------------------
If it is an XML 1.0 character, there is no need to transform it to be standard
conforming. If it is not an XML 1.0 character, you can't transmit it in a web
service String, you have to use base64.
0x27 and 0x1b are valid characters, so no need for escaping. Only <
absolutely must be escaped in PCdata.
[2] Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] |
[#xE000-#xFFFD] | [#x10000-#x10FFFF]
If your client requires these characters to be escaped, your client is
defective, I am afraid.
You could probably write an interceptor to do this additional escaping if you
need it.
> XML contains binary data (ASCII 27, ^[, ESC)
> --------------------------------------------
>
> Key: CXF-1289
> URL: https://issues.apache.org/jira/browse/CXF-1289
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.2, 2.0.3
> Reporter: Scott Anderson
>
> I've got a SOAP request that results in a string with an ESCAPE code (ASCII
> 27, ^[, ESC), and it isn't being transformed in to XML properly. CXF leaves
> it as its binary value, instead of converting to  or 
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
