[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2757:
---------------------------------------
Since there is no standard xmloutputfactory option for invalid character replacement,
odata4j does not presume the use of woodstox, and there's no simple path for user
interaction of the xmloutputfactory to set a woodstox specific property it's fairly
safe to assume that this will not be addressed as an enhancement by odata4j.
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