[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Patrick Deenen commented on TEIID-2757:
---------------------------------------
Thanks for this solution. How do I set the property with
[1] Plain HTTP client doing Odata request with a URL?
[2] Web services?
And some feedback on the change:
In Row 379 LocalClient.java - only checks for characters <= 0x0020
But I understand that there are more invalid characters in XML 1.0:
• \u007F - \u0084
• \u0086 - \u009F
• \uD800 - \uDFFF
• \uFDD0 - \uFDEF; \uFFFE; \uFFFF
Is it not safer to replace these also?
And in which enterprise version is this change to be included?
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