[
https://issues.apache.org/jira/browse/CXF-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-5522.
------------------------------
Resolution: Not A Problem
Fix Version/s: Invalid
Assignee: Daniel Kulp
This is not a problem in CXF for two reasons:
1) If this was a bug, it would be in the Stax parser that is picked up to write
XML. Usually woodstox.
2) Nothing in XML spec or anything requires that the closing > be escaped.
I'm not aware of any of the XML writer that would do that as it's a waste of
processing time and bandwidth. If it's not required, why do it?
> xs:string content not correctly escaped
> ---------------------------------------
>
> Key: CXF-5522
> URL: https://issues.apache.org/jira/browse/CXF-5522
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.7.5
> Reporter: Alex O'Ree
> Assignee: Daniel Kulp
> Fix For: Invalid
>
>
> I have a jaxws service in which the content of the string actually includes
> xml. All of the < symbols are correctly escaped, however the > symbols are
> not.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
