[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2757:
----------------------------------
Affects Version/s: 8.4
(was: 8.5)
This doesn't appear to be something that we can workaround as if we attempt to escape
the characters the escaping will be escaped. So as Ramesh is getting at this is an issue
below us. Another possible workaround is that if any of the lower ascii non-allowed
control characters are being used, then they could use a binary representation (varbinary
column) instead.
XML reserved characters not support in Odata
--------------------------------------------
Key: TEIID-2757
URL:
https://issues.jboss.org/browse/TEIID-2757
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.4
Environment: EAP version 6.1 with Teiid 8.5
Reporter: Marc Shirley
Assignee: Steven Hawkins
The odata framework sometimes has problems with transforming characters (reserved in XML)
from the source data to the XML result. The result is an exception: TEIID16013 Error
occured producing OData result.: java.lang.RuntimeException:
com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output
(in xml 1.1, could output as a character entity).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira