XML DB: XMLType encoding

Hi
I am new in using XMLDB.
I extract XML data from the db using a query like this:
select XMLElement(...).getClobVal() from...
and everything works fine.
I encontered a problem with the encoding: e.g. by default apostrophe is encoded as &apos ; while I need (in order to ensure compatibility with other applications) the numeric encoding &#39 ; .
How can I force the numerical encoding?
thanks
Giorgio
Edited by: giorgio82 on Mar 2, 2009 7:44 PM

I agree with you, but if the application is Internet Explorer 6.0....
Any idea? What can I do?
How to disable encoding at all?

Similar Messages

Importing XML data into sys.XMLType - encoding problem

Hi,
I'm using "modplsql Gateway" to upload XML file with encoding "windows-1250" with some regional characters in database table.
The table definition:
CREATE TABLE NAHRAJ_DATA (
NAME VARCHAR(128) UNIQUE NOT NULL,
MIME_TYPE VARCHAR(128),
DOC_SIZE NUMBER,
DAD_CHARSET VARCHAR(128),
LAST_UPDATED DATE,
CONTENT_TYPE VARCHAR(128),
CONTENT LONG RAW,
BLOB_CONTENT BLOB
The file was uploaded correct.
My database have
NLS_CHARACTERSET EE8MSWIN1250
NLS_NCHAR_CHARACTERSET AL16UTF16
After upload, I convert data from hex(blob) to dec and with function chr() to char. BLOB -> CLOB.
Next I create sys.XMLType from CLOB. With this progression works all in order.
In other system where are
NLS_CHARACTERSET AL32UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16
BLOB_CONTENT column(table NAHRAJ_DATA) starts with "FF FE FF FE" in HEX before my XML data. Exactly convert is OK, bud if I can create sys.XMLType I get this
ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing
LPX-00200: could not convert from encoding UTF-8 to UCS2 Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 0
ORA-06512: at line 1
I haven't any idea what's wrong.
Whats mean the HEX code in BLOB_CONTENT column after upload?
Thangs
Lukas

Please post your question in XMLDB forum

XML message without encoding type

Hi,
Is there any possibility to generate the XML file without encoding?
Should convert <?xml version="1.0"; encoding="UTF-8"?> to <?xml version="1.0";?>. I have checked the blog and the answer was either Java mapping or XSLT mapping. Is it possible to handle in graphical mapping?
I am using the AS2 adapter to send the file to customer and External defination for the target message. Below are few information on the AS2 configuration:
Signing Algorithm: SHA-1
Encryption: 3DES
Your suggestion is highly appreciated.
Regards,
Vasantha

HI Vasantha,
It is not possible with Graphical Mapping you need to go either with JAVA or XSLT mapping.
/people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean
Cheers!!!
Naveen

Psadmin list-dp : xml output is encoded with environment locale encoding

I am building some scripts to help me administer desktop profiles, providers jsp files, and others. Thoses scripts use the psadmin command.
I have hit what seems to me an unexpected behavior, when trying to download a desktop profile from a script :
the list-dp psadmin command output is encoded with the current environment locale encoding.
I suppose almost all psadmin commands localize and encode output as well, but in this case it is annoying : list-dp fails to output a valid xml file when xml header stated encoding (which is left untouched) and current locale encoding differ.
I have found a simple workaround which involve setting the environment locale to a fixed value, but I would like to know if this problem is known, and if it will be corrected (if it is not already) ?
My portal version is 7.0 with patch 121913-01,
the host system is SunOS 5.10 on a sparc host (v240).
Best Regards

Well, I have found the answer to my question :
The Sun Java System Portal Server 7.1 Release Notes bugs section refers to bug #6502307 and gives a workaround.
Here is the link to release note :
http://docs.sun.com/app/docs/doc/819-4986
and to bugs section :
http://docs.sun.com/app/docs/doc/819-4986/6n73o6vk6?a=view

[svn:fx-trunk] 13383: Modify to include the xml header (with encoding) in the DITA xml files.

Revision: 13383
Revision: 13383
Author:   [email protected]
Date:     2010-01-08 12:04:00 -0800 (Fri, 08 Jan 2010)
Log Message:
Modify to include the xml header (with encoding) in the DITA xml files.
QE notes: None.
Doc notes: None
Reviewed By: Pete
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

Thats good news.

Unable to convert BLOB to XML using XMLTYPE

Hello (XML) Experts
I need your help with manipulating a BLOB column containing XML data - I am encountering the following error:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00200: could not convert from encoding UTF-8 to WINDOWS-1252
Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 283
I am on Windows 7 64 bit, Oracle 11.2.0.3 64 bit and database character set is WE8MSWIN1252, NLS_LANG is set to AMERICAN_AMERICA.AL32UTF8. The BLOB column contains the following XML data:
ï»¿<?xml version="1.0" encoding="utf-8"?>
<Root CRC="-4065505">
<Header Converted="0">
    <Version Type="String" Value="512" />
    <Revision Type="String" Value="29" />
    <SunSystemsVersion Type="String" Value="" />
    <Date Type="String" Value="20080724" />
    <Time Type="String" Value="165953" />
    <DAG Type="String" Value="" />
    <ChkID Type="String" Value="" />
    <FormType Type="String" Value="1" />
    <DB Type="String" Value="AllBusinessUnits" />
    <FuncID Type="String" Value="SOE" />
    <Status Type="String" Value="" />
    <FileType Type="String" Value="SFL" />
    <Descriptions>
      <Default Type="String" Value="Sales Order Entry" />
      <L01 Type="String" Value="Sales Order Entry" />
      <L33 Type="String" Value="Saisie commande client" />
      <L34 Type="String" Value="Entrada de Ã³rdenes de venta" />
      <L39 Type="String" Value="Inserimento ordine di vendita" />
      <L49 Type="String" Value="AuftrÃ¤ge erfassen" />
      <L55 Type="String" Value="Entrada de pedido de venda" />
      <L81 Type="String" Value="å?—æ³¨ã‚ªãƒ¼ãƒ€ãƒ¼å…¥åŠ›" />
      <L86 Type="String" Value="é”€å”®è®¢å?•å½•å…¥" />
      <L87 Type="String" Value="éŠ·å”®è¨‚å–®éŒ„å…¥" />
    </Descriptions>
</Header>
<FormDesignerAppVer Type="String" Value="5.1" SFLOnly="1" />
</Root>I am using the XMLTYPE constructor and passing in the BLOB column and the character set id of the XML data stored in the BLOB column in order to extract and update a node in the XML as follows:
select xmltype(srce_form_detail,873) from SRCE_FORM where 873 above corresponds to the utf-8 encoding of the XML data in the BLOB column i.e. AL32UTF8, but this results in the above error.
I have also tried converting the BLOB to a CLOB first as below where BLOB2CLOB is a function that converts the BLOB to a CLOB:
select xmltype(BLOB2CLOB(srce_form_detail)).EXTRACT('/Root/Header/DB').getStringVal() XMLSrc from SRCE_FORM;This results in the following error:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00210: expected '<' instead of '¿'
Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at line 1
Looking at the XML in the BLOB I noticed that it contains a BOM(byte order mark) and this is causing the XML parsing to fail and I don't know how to deal with it and I don't want to simply SUBSTR it out.
What I am trying to achieve is to extract the contents of the DB node in the XML and depending on its value I need to update the 'Value' part of that node. I am stuck at the point of extracting the contents of the DB node.
I hope I have provided enough information and I would appreciate any suggestions on how best to resolve this - my XML knowledge is very limited so I would appreciate any help.
Regards,
Mohinder

Hi Marc
Thanks for your response.
You are correct that the blob contains Japanese and Chinese characters but I was expecting that using the XMLTYPE constructor would convert the character set albeit with some data loss or then not display the Chinese and Japanese characters correctly.
It seems to me that XMLTYPE is not handling/interpreting the BOM contained in the BLOB since even converting the BLOB to CLOB is resulting in an error. If I use SUBSTR and ignore the BOM to extract the XML from the BLOB then it works and as expected the Chinese and Japanese characters are not displayed correctly, they are displayed as '¿' corresponding to the lines beginning with L81, L86 & L87 , see below:
select xmltype(SUBSTR(BLOB2CLOB(srce_form_detail),4)) from SRCE_FORM
<?xml version="1.0" encoding="utf-8"?>
<Root CRC="-4065505">
<Header Converted="0">
    <Version Type="String" Value="512" />
    <Revision Type="String" Value="29" />
    <SunSystemsVersion Type="String" Value="" />
    <Date Type="String" Value="20080724" />
    <Time Type="String" Value="165953" />
    <DAG Type="String" Value="" />
    <ChkID Type="String" Value="" />
    <FormType Type="String" Value="1" />
    <DB Type="String" Value="AllBusinessUnits" />
    <FuncID Type="String" Value="SOE" />
    <Status Type="String" Value="" />
    <FileType Type="String" Value="SFL" />
    <Descriptions>
      <Default Type="String" Value="Sales Order Entry" />
      <L01 Type="String" Value="Sales Order Entry" />
      <L33 Type="String" Value="Saisie commande client" />
      <L34 Type="String" Value="Entrada de ¿¿rdenes de venta" />
      <L39 Type="String" Value="Inserimento ordine di vendita" />
      <L49 Type="String" Value="Auftr¿¿ge erfassen" />
      <L55 Type="String" Value="Entrada de pedido de venda" />
      <L81 Type="String" Value="¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿" />
      <L86 Type="String" Value="¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿" />
      <L87 Type="String" Value="¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿" />
    </Descriptions>
</Header>Can you please let me know how I can extract the binary dump of the BLOB and post it on the forum as I don't know how to do this. Below is snippet of the hexadecimal dump, that includes the BOM. I can post the full hexadecimal dump if this can help you to reproduce the error ?
EFBBBF3C3F786D6C2076657273696F6E3D22312E302220656E636F64696E673D227574662D38223F3E0D0A3C526F6F74204352433D222D34303635353035223E0D0A20203C48656164657220436F6E7665727465643D2230223E0D0A202020203C56657273696F6E20547970653D22537472696E67222056616C75653D2235313222202F3E0D0A202020203C5265766973696F6E20547970653D22537472696E67222056616C75653D22323922202F3E0D0A202020203C53756E53797374656D7356657273696F6E20547970653D22537472696E67222056616C75653D2222202F3E0D0A202020203C4461746520547970653D22537472696E67222056616C75653D22323030383037323422202F3E0D0A202020203C54696D6520547970653D22537472696E67222056616C75653D2231363539353322202F3E0D0A202020203C44414720547970653D22537472696E67222056616C75653D2222202F3E0D0A202020203C43686B494420547970653D22537472696E67222056616C75653D2222202F3E0D0A202020203C466F726D5479706520547970653D22537472696E67222056616C75653D223122202F3E0D0A202020203C444220547970653D22537472696E67222056616C75653D22416C6C427573696E657373556E69747322202F3E0D0A202020203C46756E63494420547970653D22537472696E67222056616C75653D22534F4522202F3E0D0A202020203C53746174757320547970653D22537472696E67222056616C75653D2222202F3E0D0A202020203C46696C655479706520547970653D22537472696E67222056616C75653D2253464C22202F3E0D0A202020203C4465736372697074696F6E733E0D0A2020202020203C44656661756C7420547970653D22537472696E67222056616C75653D2253616C6573204F7264657220456E74727922202F3E0D0A2020202020203C4C303120547970653D22537472696E67222056616C75653D2253616C6573204F7264657220456E74727922202F3E0D0A2020202020203C4C333320547970653D22537472696E67222056616C75653D2253616973696520636F6D6D616E646520636C69656E7422202F3E0D0A2020202020203C4C333420547970653D22537472696E67222056616C75653D22456E747261646120646520C3B37264656E65732064652076656E746122202F3E0D0A2020202020203C4C333920547970653D22537472696E67222056616C75653D22496E736572696D656E746F206F7264696E652064692076656E6469746122202F3E0D0A2020202020203C4C343920547970653D22537472696E67222056616C75653D224175667472C3A4676520657266617373656E22202F3E0D0A2020202020203C4C353520547970653D22537472696E67222056616C75653D22456E74726164612064652070656469646F2064652076656E646122202F3E0D0A2020202020203C4C383120547970653D22537472696E67222056616C75653D22E58F97E6B3A8E382AAE383BCE38380E383BCE585A5E58A9B22202F3E0D0A2020202020203C4C383620547970653D22537472696E67222056616C75653D22E99480E594AEE8AEA2E58D95E5BD95E585A522202F3E0D0A2020202020203C4C383720547970653D22537472696E67222056616C75653D22E98AB7E594AEE8A882E596AEE98C84E585A522202F3E0D0A202020203C2F4465736372697074696F6E733E0D0A20203C2F4865616465723E0D0A20203C466F726D3E0D0A202020203C4372656174696F6E4C616E6720547970653D22537472696E67222056616C75653D223031222053464C4F6E6C793D223122202F3E0D0A202020203C416374696F6E733E0D0A2020202020203C5065726D697373696F6E73202F3E0D0A202020203C2F416374696F6E733E0D0A202020203C48656C70202F3E0D0A202020203C466F6E743E0D0A2020202020203C446566466F6E7453697A6520547970653D22496E7465676572222056616C75653D2238222053464C4F6E6C793D223122202F3E0D0A2020202020203C466F6E743E0D0A20202020202020203C4C616E677561676520547970653D22537472696E67222056616C75653D2244656661756C7422202F3E0D0A20202020202020203C466F6E744E616D6520547970653D22537472696E67222056616C75653D224D532053616E7320536572696622202F3E0D0A2020202020203C2F466F6E743E0D0A2020202020203C466F6E743E0D0A20202020202020203C4C616E677561676520547970653D22537472696E67222056616C75653D22383122202F3E0D0A20202020202020203C466F6E744E616D6520547970653D22537472696E67222056616C75653D224D5320554920476F7468696322202F3E0D0A2020202020203C2F466F6E743E0D0A202020203C2F466F6E743E0D0A202020203C436F6E74726F6C733E0D0A2020202020203C436F6E74726F6C3E0D0A20202020202020203C436F6E74726F6C5479706520547970653D22496E746567657222204644496E743D2231222056616C75653D223122202F3E0D0A20202020202020203C446973706C61795479706520547970653D22537472696E6722204644496E743D2230222056616C75653D22466F726D2057696E646F77222053464C4F6E6C793D223122202F3E0D0A20202020202020203C43617074696F6E20547970653D22537472696E6722204644496E743D2230222056616C75653D2253597C3F7C55547C3F7C3F3F3F3F3F3F22202F3E0DThe XML I posted so far is actually truncated as the full XML is quite big but I showed the beginning of it as this is the section I believe that is not being handled properly. Furthermore I am able to write the BLOB out to a file successfully without any errors using DBMS_LOB & UTL_FILE.PUT_RAW and this seems to handle the BOM without any issues but what I really need to do is read a single node in the XML and update it directly preferably using XMLTYPE directly with the BLOB.
I would welcome your suggestions on how best to read a single node and update it when the XML is contained in a BLOB.
Regards,
Mohinder

To generate xml code in encoding as specified in system profile options

Hi,
i have a customer bug wherein the report page which is generated after a particular process, which is a .xml file, does not open because we have special characters which are not getting encoded properly!..
the probable solution to this would be to encode the .xml file in the encoding format specified in system profile options.
After the content generation the following code is used to generate the tags and the .xml page:
DBMS_XMLGEN.setRowSetTag(l_qryCtx,'INVOICE_SET');
DBMS_XMLGEN.setRowTag(l_qryCtx, 'INVOICE_RECORD');
DBMS_XMLGEN.setBindValue(l_qryCtx,'BATCH_ID', p_batch_id);
DBMS_XMLGEN.setBindValue(l_qryCtx,'SUPPLIER_ID', rec.supplier_id);
DBMS_XMLGEN.setBindValue(l_qryCtx,'SITE_ID', rec.site_id);
l_result_clob :=DBMS_XMLGEN.GETXML(l_qryCtx);
l_result_clob := substr(l_result_clob,instr(l_result_clob,'>')+1);
l_temp_invoice_count := DBMS_XMLGEN.getNumRowsProcessed(l_qryCtx);
l_invoice_count := l_invoice_count + l_temp_invoice_count;
DBMS_XMLGEN.closeContext(l_qryCtx);
clob_to_file(l_result_clob);
here we have a transaction type in portugese like Nota de Crédito
and the issue summary is as follows
It contains some foreign language symbols which are not encoded in UTF-8 format hence IE is showing the error. Even though in mozilla the file is completely opened but the same foreign language symbol is not shown. So the error exists in all the browsers.
can you please suggest how the encoding maybe done so as to avoid the above problem!...
and also how to include the encoding as per mentioned in the system profile options.

Hi,
>>>The XSD doesn't have any messages only simple and complex types - I can't seem to relate (via drag and drop) them to a data or message type to generate the required objects.
maybe it has some reference inside to some other types which you did not get?
if so you need to import into IR/ESR all files and put the correct reference (external archives)
this would be the proper way to get the file generated according to the xml schema
Regards,
Michal Krawczyk

Getting null value while parsing "XML String" with encoding WINDOWS-1252.

Hi,
when I am converting the Follwoing "xml string " to Document, I am getting the "null" as a document value.
    String strXML = "<?xml version="1.0" encoding="WINDOWS-1252"?>
                          <category name="SearchByAttributes" value="Search By Attributes">
                            <item name="ORDER_LINE_ID" description="Application Search Attributes" >
                               <attribute name="Sequence" value="0001"/>
                             </item>
                            </category>"
My "xml string" has the encoding vaule: WINDOWS-1252.
I am using the following code to convert the "xml string" to Document. I am getting the Document values as a "null" while converting the above "string xml"
        String strXML = //my above string xml.
        DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
        docBuilderFactory.setIgnoringElementContentWhitespace(true);
        docBuilder = docBuilderFactory.newDocumentBuilder();
        doc = docBuilder.parse(new InputSource(new StringReader(strXML)));
        System.out.println("doc value.."+doc)//I am getting null value for "doc".
Can anyone help me to resolve the issue.

Thagelapally wrote:
I am coverting the below "XML string" to Document, once it is converted I am reading that Document,which have an "attribue" Element in.
String strXML = "<?xml version="1.0" encoding="WINDOWS-1252"?>
<category name="SearchByAttributes" value="Search By Attributes">
<item name="ORDER_LINE_ID" description="Application Search Attributes" >
<attribute name="Sequence" value="0001"/>
</item>
</category>" I am using the above code to read the Document. When run the code in "OC4J Server" and using Jdeveloper as an editor,I am able to perfectly read the "attribute" element in the document with out any problem.Println statement printing as I expected.
System.out.println("Element Name..."+listOfAtt.getNodeName());
//getting Element Name as...."attribute"(as expected)
System.out.println("Element Attibrute list....."+elementAtt);
//getting Element Attribute list as an...."oracle.xml.parser.v2.XMLAttrList@afe"But when run the same code(reading the same Document) in Tomcat and Eclipse,println satatement not printing as i expected.
System.out.println("Element Name..."+listOfAtt.getNodeName());
//getting Element Name as...."#text"(I am expecting output value "attribute" but it is printing "#text" which i don't know)
System.out.println("Element Attibrute list....."+elementAtt);
//getting Element Attribute list as an...."null"(I am expecting output value object reference but it is printing "null"
(without the rest of the code, i'm guessing that) most likely you are grabbing the first child node of the item element. however, you are not accounting for some text nodes that are most likely in that list, like the whitespace between the item element and the attribute element. please go read some tutorials on xml, there are thousands of them out there, and they will answer all you initial questions much more efficiently than posting each step to the forums.

XML to URL Encoded (XSLT?)

I have some data in a Document object and need to convert it to URL encoded format so, for example this:
<share>
<code>GSK</code>
<price>13.34</price>
</share>
becomes something like...
&code=GSK&price=13.34& ...
I've been looking into doing this with XSLT but have run into difficulties. Do you think this is the best way of solving this problem, or is there another easier way?
Thanks.

I did something similar, basically takes a incoming XML file and output a HTML with certain link containing XML element value as query string. One of the things you have to be careful is, like Dr. Clap mentioned, to properly encode the value. I accompolished by using java extension in my XSL.
For example:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
          xmlns:encode="java.net.URLEncoder"
          extension-element-prefixes="encode"
          version="1.0">
     <xsl:template match="/">
          <xsl:variable name="myURL" select="concat('?blah=', encode:encode($myValueFromXML))" >
     </xls:template>
</xsl:stylesheet>

Embedding HTML in XML CDATA and encoding issues

Hi all,
I'm embedding HTML code in a CDATA section. My problem is that, depending on the document, the HTML can be encoded in many formats. I borrowed a piece of code that sniffs that format so i can create String in the "right" encoding (or at least the one that was guessed).
- If I directly injected those in the CDATA section, i guess they'd be encoded in UTF-8 and some character would be misinterpreted?
- What if i would transcode the HTML from the sniffed format to utf-8?
-Are there any issues woth doing this?
Sorry if this is a dumb question but I'm quite new to that kind of encoding issues.
BTW i'm using DOM.
Thanks
lexo

I don't know if it's a dumb question. I just don't understand it at all. Encoding issues only arise when you write data from a Java program to an external location, or when you read data from an external location into a Java program. And none of the activities you mentioned there have anything to do with that.
When you write your XML to an external file, or wherever you write it to, it gets encoded at that moment. The whole thing. Elements, attributes, CDATA sections, the whole thing. Doesn't matter what's in it, the whole thing gets encoded in whatever charset was chosen.
Does that help?

XML Server character encoding

Hi, I'm using the proxy generated by UDS for XML Server published service object. I have some problems with strings return types with some locales ( e.g:spanish ).
How can I set the XML Server response character encoding to avoid this problem?

This tech note will help:
http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsunone%2F7717&zone_110=7717%2A%20
ka

XML export character encoding bug

I've found a bug with Final Cut Pro XML export for any projects where media has a "#" in the name. Premiere Pro passes the "#" character into the file pathname instead of encoding it as "%23". The result is any clips with names such as "clip #1", "clip #2", "clip #3", etc. will be broken whe the XML is imported by another application. Compare:
Premiere Pro XML (does not work):
<pathurl>file://localhost/Volumes/P50%20Production%20Drive%202/CNMT%202011-12/CNMT%202011- 12%20Final%20Cut%20Pro%20Documents/Mom%20is%20Never%20Wrong/
CNMT_MomNeverWrong_Street_12_14_11/Clip%20#2.mov</pathurl>
Final Cut Pro XML (works properly):
<pathurl>file://localhost/Volumes/P50%20Production%20Drive%202/CNMT%202011-12/CNMT%202011- 12%20Final%20Cut%20Pro%20Documents/Mom%20is%20Never%20Wrong/
CNMT_MomNeverWrong_Street_12_14_11/Clip%20%232.mov</pathurl>
Note the difference in the clip name. A global search and replace of "#" with "%23" makes the Premiere Pro XML work properly.
This bug is easily repeatable and verifiable. I've filed a bug report but wanted to post here just to give folks a heads up.
Thanks for your help!
--dhl

This tech note will help:
http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsunone%2F7717&zone_110=7717%2A%20
ka

XML Parser - Character Encoding

Hi,
I am trying to parse a XML document containing Korean characters. Using XSL stylesheet to generate HTML output in Java Servlet.
How can i do to make it work?
I'm using WintNT with IIS - ServletExec3.1 for servlet engine.
Here's the error messages...
java.io.UTFDataFormatException: Invalid UTF8 encoding
at oracle.xml.parser.v2.XMLUTF8Reader.checkUTF8Byte(XMLUTF8Reader.java:65)
at oracle.xml.parser.v2.XMLUTF8Reader.readUTF8Char(XMLUTF8Reader.java:162)
at oracle.xml.parser.v2.XMLUTF8Reader.fillLastBuffer(XMLUTF8Reader.java:142)
at oracle.xml.parser.v2.XMLByteReader.fillByteBuffer(XMLByteReader.java:300)
at oracle.xml.parser.v2.XMLUTF8Reader.fillBuffer(XMLUTF8Reader.java:108)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:277)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:163)
Thanks...
TN
null

Yes, I did.
I tried with:
1. encoding="EUC-KR"
2. encoding="IOS2022KR"
3. encoding="UTF-8"
4. and some ...
but it still return the same error.
Any ideas,
Thanks,
Tuan
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by oracle xml team:
Have you set your encoding in the header of xml file?<HR></BLOCKQUOTE>
null

XML data - charset encoding problem

Hello all,
I am facing an issue on charset encoding. My requirement is to send an XML and read the the output XML to display the output. The output XML is encoded in "ISO-8859-1" and we are retrieving/reading it in "UTF-8". But some special characteres in the output XML are appearing as it is.
Could some one let me know on how to obtain the desired characters.
Code snippet while reading the XML:
BufferedReader inStream = null;
BufferedWriter outStream = new BufferedWriter(new OutputStreamWriter(connection.getOutputStream(),"UTF-8"));
inStream =
     new BufferedReader(new InputStreamReader(inputStream,"UTF-8"));
Thanks & regards,
Sharath

Hi Sharath,
To read the XML file use the following. Dont mention the character set during reading it.I hope it will help you.
XML file(emp.xml)
<?xml version="1.0" encoding="ISO-8859-1"?>
<Emp>
<EmpDetails>
       <firstname>Sarbari</firstname>
       <lastname>Saha</lastname>
</EmpDetails>
<EmpDetails>
       <firstname>Tumpa</firstname>
       <lastname>Hazra</lastname>
</EmpDetails>
</Emp>
Java File
import java.io.*;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import org.xml.sax.SAXException;
import org.w3c.dom.NamedNodeMap;
class ReadXML
     public static void main(String args[])
          try
               String fileName="emp.xml";
               DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
               DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
               Document doc = docBuilder.parse (fileName);
               NodeList nodeList = doc.getChildNodes();
               int nodeSize = nodeList.getLength();
               for (int i=0;i<nodeSize;i++)
                    Node node = nodeList.item(i);
                    Element elm = (Element) node;
                    NodeList EmpDetailsList=elm.getElementsByTagName("EmpDetails");
                    int stNodeSize = EmpDetailsList.getLength();
                    System.out.println("NodeSize = "+stNodeSize );
                    for(int j=0;j<stNodeSize;j++)
                              Node nodeEmpdtl = EmpDetailsList.item(j);
                              Element elmDetails = (Element) nodeEmpdtl;
                              NodeList firstnameList=elmDetails.getElementsByTagName("firstname");
                              NodeList lastnameList=elmDetails.getElementsByTagName("lastname");
                              Node fnameNode=firstnameList.item(0);
                              System.out.print("Node : " + fnameNode.getNodeName());
                              System.out.println (" Value : "+((Element)fnameNode).getChildNodes().item(0).getNodeValue());
                              int lastnameNodeSize = lastnameList.getLength();
                              Node lnameNode=lastnameList.item(0);
                              System.out.print("Node : " + lnameNode.getNodeName());
                              System.out.println(" Value : "+((Element)lnameNode).getChildNodes().item(0).getNodeValue());
          catch(ParserConfigurationException pce)
               System.out.println("Inside ParserConfigurationException Exception");
          catch(SAXException se)
               System.out.println("Inside SAXException Exception");
          catch(IOException ioe)
               System.out.println("Inside IOException Exception");
Regards,
Mithu

XML to DataGird encoding problem

XML is in windows-1250 encoding (beacuse special character
čćžšđ)
when I load XML into DataGrid there are no special chars like
čćžšđ

I solved this. I convert to Unicode UTF-8

XML DB: XMLType encoding

Similar Messages

Maybe you are looking for