[teiid-issues] [JBoss JIRA] (TEIID-2757) XML reserved characters not support in Odata
[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2757:
---------------------------------------
This should IMHO not be the case. I would expect enterprise
reliability from an enterprise product.
I'm not sure this reflects on reliability. This doesn't appear to be a common
case given how it is not handled by odata4j/woodstox.
That said I would settle for a simple configuration option which
enables the replacement of invalid characters by white spaces if they cannot be replaced
by XML entities.
That would only be a last resort. This could be seen as an issue for woodstox or odata4j.
From what I can see even the sun reference stax doesn't handle escaping the forbidden
control characters, so this is a general problem for xml frameworks. If workarounds such
as using JSON, a binary type, or a view to perform the necessary cleansing aren't
acceptable, then we'll want to get something logged further downstream and then
determine if there's anything we want to do on our side.
XML reserved characters not support in Odata
--------------------------------------------
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
The odata framework sometimes has problems with transforming characters (reserved in XML)
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