[
https://issues.jboss.org/browse/TEIID-3962?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3962:
---------------------------------------
Steve, are you saying this is not an issue with JSON?
JSON has different rules about string encoding. It's perfectly valid to have any
unicode characters even control characters - you can optionally encode control characters
for readability.
How about when we convert JSON to XML?
I don't think we've checked that path, but that's really a separate issue.
This issue was only logged around production of xml.
remove invalid character handling from Teiid odata4 logic
---------------------------------------------------------
Key: TEIID-3962
URL:
https://issues.jboss.org/browse/TEIID-3962
Project: Teiid
Issue Type: Quality Risk
Components: OData
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Since we now have a better influence over the odata framework, we should remove the
replacement character logic from Teiid and let that be handled by the serializers - as the
current handling is intended for XML but will affect both JSON and XML results.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)