[teiid-issues] [JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed
[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2757:
---------------------------------------
How do I set the property with
See https://docs.jboss.org/author/display/TEIID/OData+Support it is set for all odata
requests.
Is it not safer to replace these also?
There's a distinction to be made between invalid and the compatibility characters you
are mentioning. The use of compatibility characters is discouraged, but not invalid.
Thus there's no exception produced by Woodstox. As to whether it's better to
replace them as well, that doesn't seem like something that we should assume.
And in which enterprise version is this change to be included?
Again that is not a question that can be fully answered in the community. Please contact
support.
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: List of invalid XML characters.docx,
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