[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2757.
-----------------------------------
Resolution: Done
Added an odata configuration property - invalid-xml10-character-replacement - that can be
set to the desired replacement string should an invalid character be encountered.
Unfortunately this affects both xml and json results. The default behavior remains as
throwing an exception. Users can also use the workarounds listed in this issue.
XML 1.0 invalid characters not supported in Odata Atom feed
-----------------------------------------------------------
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
Fix For: 8.7
Attachments: TEIID-2757-Webservices-Stacktrace.txt
The odata framework sometimes has problems with transforming characters (invalid in XML
1.0) 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