[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2757:
---------------------------------------
Does this fix also resolves the problem with web services?
No. I wasn't ignoring your comment, it's just as this was logged against OData it
wasn't clear the context was. In any case with other access paths where the xml
generation is explicit and given the uncommonness of data it would seem this would be an
optional enhancement where having the user perform the desired cleansing is a more
acceptable workaround. Feel free to log other issues if you see a need though.
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