Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-2118

XML encoding in Resteasy webservices

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.2
    • 7.7
    • Common
    • None
    • Workaround Exists
    • Hide

      An xml declaration with encoding can be created with:

      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)

      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.

      Show
      An xml declaration with encoding can be created with: 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) 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.

    Description

      Publishing a result procedure in a REST Service generated by "Generate RestEasyWay" functionality an Error "lectura XML: mal formado" appears.
      Executing this procedure of this service in the designer there're no errors

      Attachments

        Issue Links

          Activity

            People

              rhn-engineering-shawkins Steven Hawkins
              mlopezal_jira Mónica L.A. (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: