[ https://issues.jboss.org/browse/TEIID-2118?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2118: ---------------------------------- Workaround Description: An xml declaration with encoding can be created with: {code:sql}XMLPARSE(DOCUMENT XSLTRANSFORM(doc, '<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="xml" version="1.0" encoding="iso-8859-1"/> <xsl:template match="/"><xsl:copy-of select="/"/></xsl:template></xsl:stylesheet>' ) WELLFORMED){code} Where doc references the SQLXML doc/element to modify. Note that this workaround assumes that the user knows the encoding that will be eventually used for the xml value - making the sql environmentally dependent. Workaround: Workaround Exists Forum Reference: https://community.jboss.org/thread/203061?tstart=0 (was: https://community.jboss.org/thread/203061?tstart=0) A general solution to specifying the encoding would be through the use of a binary xmlserialize, which explicitly takes an encoding. However to utilize such logic the rest support would either need to accept blobs. Alternatively the rest support could be enhanced to specify the encoding - these options should be looked as in TEIIDDES-1460 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-2118?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2118. --------------------------------- -- 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