[
https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin...
]
Patrick Deenen edited comment on TEIID-2757 at 12/5/13 9:55 AM:
----------------------------------------------------------------
I originally added this issue to the customer portal, which is transferred here by Marc.
I understand that this is a limitation of XML, hence it may not be classified as a bug.
But it does limit the use of TEIID in real business scenarios where the source data is not
cleaned or prepared for XML as is the case for our current customer.
I do have requested to the customer to update the ETL processing to remove invalid
characters, but still feels not comfortable because simple characters in the source data
can break the system. This should IMHO not be the case. I would expect enterprise
reliability from an enterprise product.
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.
was (Author: pdeenen):
I originally added this issue to the customer portal, which transferred here by Marc.
I understand that this is a limitation of XML, hence it may not be classified as a bug.
But it does limit the use of TEIID in real business scenarios where the source data is not
cleaned or prepared for XML as is the case for our current customer.
I do have requested to the customer to update the ETL processing to remove invalid
characters, but still feels not comfortable because simple characters in the source data
can break the system. This should IMHO not be the case. I would expect enterprise
reliability from an enterprise product.
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.
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