Set XML encoding by saving with Xerces

hi there,
i parse a xml dokument which is encoded by Cp1252. then i do a lot of modifications an want to write it back by using
OutputFormat format = new OutputFormat(XmlParser.document);
format.setLineSeparator(LineSeparator.Windows);
format.setIndenting(true);
format.setLineWidth(0);
format.setPreserveSpace(true);
XMLSerializer serializer;
     try {
          serializer = new XMLSerializer(new FileWriter(file), format);
          serializer.asDOMSerializer();
          serializer.serialize(XmlParser.document);
     } catch (IOException e) {
          e.printStackTrace();
     }but this sets the encoding to UTF-8. what should i change to save it with Cp1252 encoding?

use the -
OutputFormat(org.w3c.dom.Document doc, java.lang.String encoding, boolean indenting)
constructor with encoding="windows-1252"....

Similar Messages

Setting xml encoding with documentbuilderfactory

hi everybody,
i have a problem with xml document generated by documentbuilderfactory class.
it seems that the default setting for the xml document encoding is UTF-8. i need to set this to UTF-16.
does anybody know how can i do this ?
thanx
Ale

http://forum.java.sun.com/thread.jsp?forum=34&thread=289433

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
 StringBuffer xmlStrBuf = new StringBuffer();
 TransformerFactory tFactory = null;
 Transformer transformer = null;
 Document document = null;
 public void performTest()
 xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
 .append("<TESTXML>\n")
 .append("<ELEM ATT1=\"Yes\" />\n")
 .append("</TESTXML>\n");
 // the encoding is set to iso-8859-1 in the xml declaration.
 System.out.println("initial xml = \n" + xmlStrBuf.toString());
 try
 //Test1: Use the transformer to ouput the xmlStrBuf.
 // This shows the xml encoding result from the transformer which will change to UTF-8
 tFactory = TransformerFactory.newInstance();
 transformer = tFactory.newTransformer();
 StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
 System.out.println("Test1 result = ");
 transformer.transform( ss, new StreamResult(System.out));
 //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
 DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder = dfactory.newDocumentBuilder();
 document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
 // skip adding attribute since it does not affect the test result
 // Use a Transformer to output the DOM document. the encoding becomes UTF-8
 DOMSource source = new DOMSource(document);
 StreamResult result = new StreamResult(System.out);
 System.out.println("\n\nTest2 result = ");
 transformer.transform(source, result);
 catch (Exception e)
 System.out.println("<performTest> Exception caught. " + e.toString());
 public static void main( String arg[])
 XmlEncodingTest xmlTest = new XmlEncodingTest();
 xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
 StringBuffer xmlStrBuf = new StringBuffer();
 TransformerFactory tFactory = null;
 Document document = null;
 public void performTest()
 xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
 .append("<TESTXML>\n")
 .append("<ELEM ATT1=\"Resoluci�n\">\n")
 .append("Special charatered attribute test")
 .append("\n</ELEM>")
 .append("\n</TESTXML>\n");
 // the encoding is set to iso-8859-1 in the xml declaration.
 System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
 try
 //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
 //Test1: Use the transformer to ouput the xmlStrBuf.
 tFactory = TransformerFactory.newInstance();
 Transformer transformer = tFactory.newTransformer();
 byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
 StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
 ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
 Properties transProperties = transformer.getOutputProperties();
 transProperties.list( System.out); // prints out current transformer properties
 System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
 transformer.setOutputProperty("encoding", "ISO-8859-1");
 transformer.transform( streamSource, new StreamResult( xmlBaos));
 System.out.println("**** Test1 result = ");
 System.out.println(xmlBaos.toString("ISO-8859-1"));
 //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
 DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder = dfactory.newDocumentBuilder();
 document = builder.parse( new ByteArrayInputStream( xmlbytes));
 // skip adding attribute since it does not affect the test result
 // Use a Transformer to output the DOM document.
 DOMSource source = new DOMSource(document);
 xmlBaos.reset();
 transformer.transform( source, new StreamResult( xmlBaos));
 System.out.println("\n\n****Test2 result = ");
 System.out.println(xmlBaos.toString("ISO-8859-1"));
 //xmlBaos.flush();
 //xmlBaos.close();
 catch (Exception e)
 System.out.println("<performTest> Exception caught. " + e.toString());
 finally
 public static void main( String arg[])
 XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
 xmlTest.performTest();
}

Have XML with another embedded XML encoded in base64 - how to extract?

Hi guys,
I have a XML-RPC web service that returns a response like this:
<methodResponse>
<params>
<param>
<value>
<base64>
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNlYXJjaFJlc3VsdD48bnVtcm93cz4xPC9udW1yb3dzPjxmb3VuZD4xPC9mb3VuZD48d29yZGluZm8+IGJvdMOjbyA6IDU8L3dvcmRpbmZvPjxzZWFyY2h0aW1lPjAuMDA2PC9zZWFyY2h0aW1lPjxmaXJzdGRvYz4xPC9maXJzdGRvYz48bGFzdGRvYz4xPC9sYXN0ZG9jPjx3b3JkaW5mb2FsbD5ib3TDo28gOiA1IC8gNTwvd29yZGluZm9hbGw+PGl0ZW0+PHVybGlkPjE5PC91cmxpZD48dXJsPmh0dHA6Ly9jZW50cmFsL2dhcnJhcy9RdWVtX21hdG91X0pGSy9hcnRlZmF0b3MvaHRtLzc1MDUuaHRtPC91cmw+PGNvbnRlbnQ+dGV4dC9odG1sPC9jb250ZW50Pjx0aXRsZT5Tb3VuZE1BWDwvdGl0bGU+PGtleXdvcmRzPjwva2V5d29yZHM+PGRlc2M+PC9kZXNjPjx0ZXh0Pi4uLiBlIGNvbXVuaWNhw6fDo28gdmlhIEludGVybmV0LiBDbGlxdWUgbm8gJmx0O2ZvbnQgY29sb3I9JnF1b3Q7MDAwMDg4JnF1b3Q7Jmd0OyZsdDtiJmd0O2JvdMOjbyZsdDsvYiZndDsmbHQ7L2ZvbnQmZ3Q7IGNvbSBvIGxvZ290aXBvIEFuZHJlYSBlbSAuLi4gYWRxdWlyaXIgdW1hIGF0dWFsaXphw6fDo28sIGNsaWNhbmRvIG5vICZsdDtmb250IGNvbG9yPSZxdW90OzAwMDA4OCZxdW90OyZndDsmbHQ7YiZndDtib3TDo28mbHQ7L2ImZ3Q7Jmx0Oy9mb250Jmd0OyBjb20gbyDDrWNvbmUgRm9uZSBkZSBvdXZpZG8uIERlcG9pcyBkZSAuLi4gJyBWaXJ0dWFsIEVhcicnICwgYmFzdGFuZG8gY2xpY2FyIG5vICZsdDtmb250IGNvbG9yPSZxdW90OzAwMDA4OCZxdW90OyZndDsmbHQ7YiZndDtib3TDo28mbHQ7L2ImZ3Q7Jmx0Oy9mb250Jmd0OyBjb20gw61jb25lIE91dmlkby4gQXDDs3MgYWRxdWlyaXIgZSA8L3RleHQ+PHNpemU+MTg1MDM8L3NpemU+PHJhdGluZz41LjUwNSU8L3JhdGluZz48bW9kaWZpZWQ+MTAvMDgvMjAwMiAxNjo1ODoxMCAtMDQwMDwvbW9kaWZpZWQ+PG9yZGVyPjE8L29yZGVyPjxjcmM+LTE5NjM3MDA5MzQ8L2NyYz48Y2F0ZWdvcnk+PC9jYXRlZ29yeT48bGFuZz5lbi11czwvbGFuZz48Y2hhcnNldD53aW5kb3dzLTEyNTI8L2NoYXJzZXQ+PHNpdGVpZD40NjE1ODk0NjE8L3NpdGVpZD48cG9wX3Jhbms+MC4wMDAwMDwvcG9wX3Jhbms+PG9yaWdpbmlkPjA8L29yaWdpbmlkPjwvaXRlbT48L3NlYXJjaFJlc3VsdD4K
</base64>
</value>
</param>
</params>
</methodResponse>The base64 value is another XML embedded document that I have to extract.
I have the following code (don't know if it's the best approach), where l_val is a CLOB and l_xml is XMLTYPE:
l_val := DBMS_XMLGEN.convert( l_xml.extract('/methodResponse/params/param/value/base64/text()').getclobval(), 1 );How can I decode the base64-encoded contents of the l_val CLOB and store the result into another CLOB that I can then process with xmlsequence() and extract()?
Thanks in advance. Regards,
Georger

Hi mdrake,
I saw your answer on the other thread :)
I know about the 32K limitation; that's why I need to store the decoded CLOB in another CLOB, as bigger documents will often be the case. I've been reading about this for a while, to no avail.
Do you believe BASE64_DECODE_CLOB could be changed to return CLOB rather than VARCHAR2? Regards,
Georger
mdrake wrote:
You'll need to do some work in this if the Encoded XML is bigger than 32K
SQL> set long 10000 pages 0
SQL> CREATE OR REPLACE FUNCTION BASE64_DECODE_CLOB (INPUT CLOB)
2 return VARCHAR2
3 as
4 V_RAW_BUFFER RAW(32767);
5 V_VARCHAR2_BUFFER VARCHAR2(32767);
6 begin
7 V_VARCHAR2_BUFFER := DBMS_LOB.SUBSTR(INPUT,32767,1);
8 V_RAW_BUFFER := UTL_RAW.CAST_TO_RAW(V_VARCHAR2_BUFFER);
9 V_RAW_BUFFER := UTL_ENCODE.BASE64_DECODE(V_RAW_BUFFER);
10 V_VARCHAR2_BUFFER := UTL_RAW.CAST_TO_VARCHAR2(V_RAW_BUFFER);
11 return V_VARCHAR2_BUFFER;
12 end;
13 /
Function created.
SQL> set serveroutput on
SQL> --
SQL> with XML as
2 (
3 select XMLType(
4 '<methodResponse>
5 <params>
6 <param>
7 <value>
8 <base64>
9 PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNlYXJjaFJlc3VsdD48bnVtcm93cz4xPC9udW1yb3dzPjxmb3VuZD4xPC9mb3VuZD48d29yZGl
uZm8+IGJvdMOjbyA6IDU8L3dvcmRpbmZvPjxzZWFyY2h0aW1lPjAuMDA2PC9zZWFyY2h0aW1lPjxmaXJzdGRvYz4xPC9maXJzdGRvYz48bGFzdGRvYz4xPC9sYXN0ZG9jPjx
3b3JkaW5mb2FsbD5ib3TDo28gOiA1IC8gNTwvd29yZGluZm9hbGw+PGl0ZW0+PHVybGlkPjE5PC91cmxpZD48dXJsPmh0dHA6Ly9jZW50cmFsL2dhcnJhcy9RdWVtX21hdG9
1X0pGSy9hcnRlZmF0b3MvaHRtLzc1MDUuaHRtPC91cmw+PGNvbnRlbnQ+dGV4dC9odG1sPC9jb250ZW50Pjx0aXRsZT5Tb3VuZE1BWDwvdGl0bGU+PGtleXdvcmRzPjwva2V
5d29yZHM+PGRlc2M+PC9kZXNjPjx0ZXh0Pi4uLiBlIGNvbXVuaWNhw6fDo28gdmlhIEludGVybmV0LiBDbGlxdWUgbm8gJmx0O2ZvbnQgY29sb3I9JnF1b3Q7MDAwMDg4JnF
1b3Q7Jmd0OyZsdDtiJmd0O2JvdMOjbyZsdDsvYiZndDsmbHQ7L2ZvbnQmZ3Q7IGNvbSBvIGxvZ290aXBvIEFuZHJlYSBlbSAuLi4gYWRxdWlyaXIgdW1hIGF0dWFsaXphw6f
Do28sIGNsaWNhbmRvIG5vICZsdDtmb250IGNvbG9yPSZxdW90OzAwMDA4OCZxdW90OyZndDsmbHQ7YiZndDtib3TDo28mbHQ7L2ImZ3Q7Jmx0Oy9mb250Jmd0OyBjb20gbyD
DrWNvbmUgRm9uZSBkZSBvdXZpZG8uIERlcG9pcyBkZSAuLi4gJyBWaXJ0dWFsIEVhcicnICwgYmFzdGFuZG8gY2xpY2FyIG5vICZsdDtmb250IGNvbG9yPSZxdW90OzAwMDA
4OCZxdW90OyZndDsmbHQ7YiZndDtib3TDo28mbHQ7L2ImZ3Q7Jmx0Oy9mb250Jmd0OyBjb20gw61jb25lIE91dmlkby4gQXDDs3MgYWRxdWlyaXIgZSA8L3RleHQ+PHNpemU
+MTg1MDM8L3NpemU+PHJhdGluZz41LjUwNSU8L3JhdGluZz48bW9kaWZpZWQ+MTAvMDgvMjAwMiAxNjo1ODoxMCAtMDQwMDwvbW9kaWZpZWQ+PG9yZGVyPjE8L29yZGVyPjx
jcmM+LTE5NjM3MDA5MzQ8L2NyYz48Y2F0ZWdvcnk+PC9jYXRlZ29yeT48bGFuZz5lbi11czwvbGFuZz48Y2hhcnNldD53aW5kb3dzLTEyNTI8L2NoYXJzZXQ+PHNpdGVpZD4
0NjE1ODk0NjE8L3NpdGVpZD48cG9wX3Jhbms+MC4wMDAwMDwvcG9wX3Jhbms+PG9yaWdpbmlkPjA8L29yaWdpbmlkPjwvaXRlbT48L3NlYXJjaFJlc3VsdD4K
10 </base64>
11 </value>
12 </param>
13 </params>
14 </methodResponse>') OBJECT_VALUE
15 from dual
16 )
17 select XMLSERIALIZE(DOCUMENT XMLTYPE(BASE64_DECODE_CLOB(extract(OBJECT_VALUE,'/methodResponse/params/param/value/base64/text()'
).getClobVal())) as CLOB INDENT SIZE=2)
18 from XML
19 /
<?xml version="1.0" encoding="UTF-8"?>
<searchResult>
<numrows>1</numrows>
<found>1</found>
<wordinfo> botπo : 5</wordinfo>
<searchtime>0.006</searchtime>
<firstdoc>1</firstdoc>
<lastdoc>1</lastdoc>
<wordinfoall>botπo : 5 / 5</wordinfoall>
<item>
<urlid>19</urlid>
<url>http://central/garras/Quem_matou_JFK/artefatos/htm/7505.htm</url>
<content>text/html</content>
<title>SoundMAX</title>
<keywords/>
<desc/>
<text>... e comunicaτπo via Internet. Clique no botπo com o logotipo Andrea em ... adqu
irir uma atualizaτπo, clicando no 
botπo com o φcone Fone de ouvido. Depois de ... ' Vi
rtual Ear'' , bastando clicar no 
botπo com φcone Ouvido. Ap≤s adquirir e </text>
<size>18503</size>
<rating>5.505%</rating>
<modified>10/08/2002 16:58:10 -0400</modified>
<order>1</order>
<crc>-1963700934</crc>
<category/>
<lang>en-us</lang>
<charset>windows-1252</charset>
<siteid>461589461</siteid>
<pop_rank>0.00000</pop_rank>
<originid>0</originid>
</item>
</searchResult>
SQL>And don't expect it to be the fastest soln in history.

Inserting XML encoded ampersands into tables with OracleXMLSave / XMLLoader

Hi,
I've an XMLLoader application based on Steve Muench's design.
My client has given me XML documents with XML encoded ampersands.
The XMLloader (OracleXMLSave) is treating the ampersand as a substitution token and is adding chunks of unexpected text when it inserts the strings containing ampersands.
How do I turn off the substition within the JDBC?
Thanks,
Steve.

If your XML Document looks like:
<ROWSET>
<ROW>
<FIELD1>val-1</FIELD1>
<FIELD12>val-12</FIELD12>
</ROW>
</ROWSET>
it will insert into just those two
fields, the rest will be null for
the purposes of the insert.

Different take on XML encoding character emcoding problem

I have the common problem of using non latin characters in my XML code. The XML file is saved in iso-8859-1 format and that is fine when viewing it through an editor. When i try to parse the file, no errors are reported but the special characters are changed into question marks. These characters exist in attributes, they are not content.
This happens when i am looking at the tree through DOM. In other words, I am not even outputting the tree to file. When I do a print statement on the content of the attribute, it comes out as question marks.
Therefore the standard answer of setting the encoding of the outputter does not work for me. The moment that the file is parsed in and is still in memory, the xml parser changes teh characters to question marks.
I am using the latest version of xerces and jaxp with java se 1.4.1
Can anyone help with this urgent problem?

No, I just use a simple System.out.println() statement.
Here it is printing out question marks and that is why even before i output the document the problem arises. Try this
System.out.println(new String(YOUR_STRING.getBytes("UTF8")));

Serializing, XML Encoding

Hi,
I have a GUI, letting the user the ability to save/open
a file that the application should save/-read to fill- the GUI
fields.
Instead of creating my own file with its format I decided to go for
serialization (my first attempt)
I tried to use the Serialization process, but understood that
XML encoding was more appropriate.
Anyway I first tried with Serialization by simply making
my objects implementing Serializable interface
(but not adding the writeObject and readObject methods)
But I encountered a problem :
My JtextAreas which are set transparent and disabled at gui construction
seem to become opaque when saved because their default white background
appears after save and seem to be saved as opaque because
they also show their white background when I open the serialized gui.
Note that it might not be the only strange behaviour but it is the first I saw.
Any idea on this ?
Then I tried XML encoding but then when trying to save I have the following
error messages:
java.lang.InstantiationException: javax.swing.AncestorNotifier
Continuing ...
java.lang.Exception: discarding statement DistributionTab0.addPropertyChangeListener(AncestorNotifier0);
displayed several times with the value after AncestorNotifier increasing.
And where DistributionTab is a tab of a JTabbedPanel.
I don't understand anything about this.
I do not use anywhere in the code PropertyChangeListener.
Any idea is appreciated.
thanks

If you are talking about saving user preferences for how your GUI is set up (eg: the bounds of your frame,
whether or not a toolbar is visible, various checkboxes, etc...) I would use java.util.prefs: http://java.sun.com/j2se/1.4.2/docs/guide/lang/preferences.html

XML encoding "UTF-8" ignored

HI all,
we try to post an XML message (cXML invoice) to a receiver but it doesn´t work.
We use a communication channel "http-destination" where we configure content-type "text/xml" together with XML encoding "UTF-8".
The configured URL works fine and can be tested in SM59.
The XML payload itself has a declaration <?xml version="1.0" encoding="UTF-8"?>
but the strange thing that happens is that all these declarations are being ignored and instead US-ASCII is used. Which leads to an error due to some special german characters within the contents of the XML (e.g. ä, ö, etc.).
Does anybody of you know how I can achieve that the pre-set UTF-8 will be used as encoding type???
Many thanky in advance!
Willi Wuerstlin

Hi.
I am trying to map the standard cXML invoice to SAP's standard idoc INVOIC01 - This is how the file looks like
<?xml version="1.0" ?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.014/InvoiceDetail.dtd">
<cXML version="" payloadID="2008-07-29T04:51:08-06:00.cXML.TEST4101V002" timestamp="2008-07-29T04:51:08-06:00" xml:lang="en-US">
<Header>...</Header>
...</cxml>
I am having problem with the line <!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.014/InvoiceDetail.dtd"> - when the payload is having this line XI is not accepting the message.
Please let me know how to address this.
Thanks.

XML Encoding Issue - Format UTF-16 to ISO-8859-1

Dear Groupmates,
I have data in my Internal table which i am converting to XML using custom Transformation.
Data is going to third party.The third party system requires data in ISO-8859-1 Format but SAP is generating the same in UTF-16 Format.I have been able to change the format of file from
utf-16 to ISO-8859-1 format but after conversion i am getting invalid tag information in form of characters
like &lt , &gt etc..in my file.
Here is the code i have used to set the encoding to ISO-8859-1 :-
DATA: xmlout TYPE xstring.
DATA: ixml TYPE REF TO if_ixml,
streamfactory TYPE REF TO if_ixml_stream_factory,
encoding TYPE REF TO if_ixml_encoding,
ixml_ostream TYPE REF TO if_ixml_ostream.
ixml = cl_ixml=>create( ).
streamfactory = ixml->create_stream_factory( ).
ixml_ostream = streamfactory->create_ostream_xstring( xmlout ).
encoding = ixml->create_encoding(
character_set = 'ISO-8859-1' byte_order = 0 ).
ixml_ostream->set_encoding( encoding = encoding ).
Sample Output :-
<?xml version="1.0" encoding="iso-8859-1"?>
<AMS_DOC_XML_EXPORT_FILE><AMS_DOCUMENT AUTO_DOC_NUM="FALSE" DOC_CAT="CA" DOC_CD="CA" DOC_DEPT_CD="045" DOC_ID="XR10281060830400001" DOC_IMPORT_MODE="OE" DOC_TYP="CH" DOC_UNIT_CD ="NULL" DOC_VERS_NO="01">
<CH_DOC_HDR AMSDataObject="Y">
<DOC_CAT Attribute="Y"><![CDATA[CA]]></DOC_CAT>
<DOC_TYP Attribute="Y"><![CDATA[CH]]></DOC_TYP>
Please let me know if anyone has idea how i can get rid of the invalid tag information.
Thanks !
With Regards,
Darshan Mulmule

Darshan,
Did you get an answer for this question? We have same requirement to create XML file in ISO-8859-1 format with Attributes is set to "Y" and CDATA is being used for data.
Can you please let me know if you still remember how did you achieve it?
Satyen...

How to set default encoding and charsets for jsp and servlets.

Hi,
Is there any possibility to set default encoding or charset for jsps and servlest (for both request and response)?
For example in Weblogic such parameters can be set in weblogic specific configuration files (weblogic.xml).
Thanks in advance.

Hi,
I created one request with logo in the header an page in the footer etc. and called StyleSheet. After you can import this formats by each request.
You can do this in compound layout.
Regards,
Stefan

IsSchemaValid does chang the xml-encoding header from UTF-8 to WINDOWS-1252

I found the following effect:
isSchemaValid does changing the encoding - entry of the xml-file-header
generating xml-file by using DBMS_XMLGEN :
xmldoc := DBMS_XMLGEN.getXML(ctx);
with the header of the file is
<?xml version="1.0" encoding="UTF-8"?>
change the xmldoc to a xmlType
and validate it against the schema
xmldoc_xmlType:=(xmltype(xmldoc)) ;
xmldoc_xmlType.isSchemaValid ( bSchemalocation)
after this the header of the file is
<?xml version="1.0" encoding="WINDOWS-1252"?>
my DB:
R11_2_0_2 / Windows 64
the same in
R11_2_0_1 / Windows 32
select name, value from v$parameter where upper(name) like '%NLS%'
nls_calendar
nls_comp BINARY
nls_currency
nls_date_format
nls_date_language
nls_dual_currency
nls_iso_currency
nls_language AMERICAN
nls_length_semantics BYTE
nls_nchar_conv_excp FALSE
nls_numeric_characters
nls_sort
nls_territory AMERICA
nls_time_format
nls_timestamp_format
nls_timestamp_tz_format
nls_time_tz_format
register my schema by:
dbms_xmlschema.registerSchema(
schemaurl => vschemaurl,
schemadoc => xsd_file,
local => FALSE,
gentypes => TRUE,
genbean => FALSE,
gentables => TRUE,
force => FALSE,
owner => dbuser
,CSID => nls_charset_id('AL32UTF8')
How can I let or change back the xml-encoding entry to UTF-8 ?
regards

Your solution should not be relied upon...
C:\Temp>sqlplus /nolog @t1 %CD%
SQL*Plus: Release 11.2.0.2.0 Production on Fri Mar 4 09:41:32 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
SQL> spool testcase.log
SQL> --
SQL> connect sys/oracle as sysdba
Connected.
SQL> --
SQL> set define on
SQL> set timing on
SQL> --
SQL> def XMLDIR = &1
SQL> --
SQL> def USERNAME = XDBTEST
SQL> --
SQL> def PASSWORD = &USERNAME
SQL> --
SQL> def USER_TABLESPACE = USERS
SQL> --
SQL> def TEMP_TABLESPACE = TEMP
SQL> --
SQL> drop user &USERNAME cascade
2 /
old 1: drop user &USERNAME cascade
new 1: drop user XDBTEST cascade
User dropped.
Elapsed: 00:00:00.24
SQL> grant create any directory, drop any directory, connect, resource, alter session, create view to &USERNAME identified by &PASSWORD
2 /
old 1: grant create any directory, drop any directory, connect, resource, alter session, create view to &USERNAME identified by &PASSWORD
new 1: grant create any directory, drop any directory, connect, resource, alter session, create view to XDBTEST identified by XDBTEST
Grant succeeded.
Elapsed: 00:00:00.07
SQL> alter user &USERNAME default tablespace &USER_TABLESPACE temporary tablespace &TEMP_TABLESPACE
2 /
old 1: alter user &USERNAME default tablespace &USER_TABLESPACE temporary tablespace &TEMP_TABLESPACE
new 1: alter user XDBTEST default tablespace USERS temporary tablespace TEMP
User altered.
Elapsed: 00:00:00.00
SQL> set long 100000 pages 0 lines 256 trimspool on timing on
SQL> --
SQL> connect &USERNAME/&PASSWORD
Connected.
SQL> --
SQL> create or replace directory XMLDIR as '&XMLDIR'
2 /
old 1: create or replace directory XMLDIR as '&XMLDIR'
new 1: create or replace directory XMLDIR as 'C:\Temp'
Directory created.
Elapsed: 00:00:00.00
SQL> create table XML_DEFAULT of XMLTYPE
2 /
Table created.
Elapsed: 00:00:00.11
SQL> create table XML_CLOB of XMLTYPE
2 XMLTYPE store as CLOB
3 /
Table created.
Elapsed: 00:00:00.01
SQL> select *
2 from nls_database_parameters
3 where parameter in ('NLS_LANGUAGE', 'NLS_TERRITORY', 'NLS_CHARACTERSET')
4 /
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CHARACTERSET AL32UTF8
Elapsed: 00:00:00.02
SQL> declare
2 XML_DEFAULT XMLType := xmltype('<?xml version="1.0" encoding="WINDOWS-1252"?><TEST>SELECT</TEST>') ;
3 XML_CLOB XMLType := xmltype('<?xml version="1.0" encoding="WINDOWS-1252"?><TEST>SELECT</TEST>') ;
4 begin
5 delete XML_DEFAULT;
6 delete XML_CLOB;
7 insert into XML_DEFAULT values (XML_DEFAULT);
8 dbms_xslprocessor.clob2file( XML_DEFAULT.getclobval() , 'XMLDIR','XML_DEFAULT.xml');
9 IF XML_DEFAULT.isSchemaValid ( 'SCHEMALOCATION_DOES_NO_MATTER_FOR_TEST_CASE.XSD', 'SCHEMA_NO_MATTER') = 1 THEN null; ELSE null; END IF;
10 commit;
11 dbms_xslprocessor.clob2file( XML_DEFAULT.getclobval() , 'XMLDIR','XML_DEFAULT_IS_VALID.xml',nls_charset_id('WE8MSWIN1252'));
12 dbms_xslprocessor.clob2file( XML_DEFAULT.getclobval() , 'XMLDIR','XML_DEFAULT_WIN1252.xml');
13 insert into XML_CLOB values (XML_CLOB);
14 dbms_xslprocessor.clob2file( XML_CLOB.getclobval() , 'XMLDIR','XML_CLOB.xml');
15 commit;
16 end ;
17 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.27
SQL> --
SQL> host type XML_DEFAULT.xml
<?xml version="1.0" encoding="WINDOWS-1252"?><TEST>SELECT</TEST>
SQL> --
SQL> host type XML_DEFAULT_IS_VALID.xml
<?xml version="1.0" encoding="UTF-8"?>
<TEST>SELECT</TEST>
SQL> --
SQL> host type XML_DEFAULT_WIN1252.xml
<?xml version="1.0" encoding="UTF-8"?>
<TEST>SELECT</TEST>
SQL> --
SQL> host type XML_CLOB.xml
<?xml version="1.0" encoding="WINDOWS-1252"?><TEST>SELECT</TEST>
SQL> --
SQL>First, the character set changes because isSchemaValid() causes the document to be parsed and converted to the internal database character set, as does storing it in a table.
It appear that your solution works in SQL because the semantics of SQL are such that it causes a 'copy' of the XMLType to take place before running the isSchemaValid() processing, were we to optimize away that copy as a result of a patch or performance optimization project then you solution would break...
If you want the output in a particular character set you should force that using XMLSerialize or getBlobVal(charsetid). Unfortunately we don't have a convience method for writing BLOBS on DBMS_XSLPROCESSOR...

Xmlparserv2.jar with xerces and xalan

Hello,
I have a Spring/Spring Web Flow application. I also have a separate web application that's using the XML Publisher API to generate reports from RTF files. I am now in the process of merging these two into one application.
The Spring app requires the xerces.jar and xalan.jar JARs in order to parse the various XML files required to configure Spring. The XML Publisher app requires the xmlparserv2.jar JAR in order to parse the XML required for generating reports.
When I have all of these JARs in my one web application, I receive an error when I call the FOProcessor.generate() method. Here it is:
oracle.xml.parser.v2.XMLParseException: Bad character (1).
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:324)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:287)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:292)
 at oracle.xml.parser.v2.XSLProcessor.newXSLStylesheet(XSLProcessor.java:590)
 at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:260)
 at oracle.apps.xdo.common.xml.XSLTClassic.transform(XSLTClassic.java:200)
 at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:174)
 at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1022)
 at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:968)
 at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:209)
 at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1561)
 at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:951)
I was thinking this was because there was a conflict between xalan, xerces and xmlparserv2, so I removed the xalan and xerces JARs from the classpath. Now I get the following whenever I try to hit one of my spring MVC actions:
DEBUG org.springframework.beans.factory.xml.DelegatingEntityResolver(99) - Attempting to resolve XML Schema [http://www.springframework.org/schema/beans/spring-beans-2.0.xsd] using [org.springframework.beans.factory.xml.PluggableSchemaResolver]
<Line 43, Column 57>: XML-24509: (Error) Duplicated definition for: 'identifiedType'
<Line 60, Column 28>: XML-24509: (Error) Duplicated definition for: 'beans'
<Line 145, Column 34>: XML-24509: (Error) Duplicated definition for: 'description'
<Line 158, Column 29>: XML-24509: (Error) Duplicated definition for: 'import'
<Line 180, Column 28>: XML-24509: (Error) Duplicated definition for: 'alias'
<Line 209, Column 33>: XML-24509: (Error) Duplicated definition for: 'beanElements'
<Line 223, Column 44>: XML-24509: (Error) Duplicated definition for: 'beanAttributes'
<Line 486, Column 43>: XML-24509: (Error) Duplicated definition for: 'meta'
<Line 494, Column 35>: XML-24509: (Error) Duplicated definition for: 'metaType'
<Line 511, Column 27>: XML-24509: (Error) Duplicated definition for: 'bean'
<Line 531, Column 38>: XML-24509: (Error) Duplicated definition for: 'constructor-arg'
<Line 600, Column 51>: XML-24509: (Error) Duplicated definition for: 'property'
<Line 611, Column 36>: XML-24509: (Error) Duplicated definition for: 'lookup-method'
<Line 647, Column 38>: XML-24509: (Error) Duplicated definition for: 'replaced-method'
<Line 684, Column 31>: XML-24509: (Error) Duplicated definition for: 'arg-type'
<Line 711, Column 26>: XML-24509: (Error) Duplicated definition for: 'ref'
<Line 749, Column 28>: XML-24509: (Error) Duplicated definition for: 'idref'
<Line 783, Column 28>: XML-24509: (Error) Duplicated definition for: 'value'
<Line 811, Column 27>: XML-24509: (Error) Duplicated definition for: 'null'
<Line 825, Column 39>: XML-24509: (Error) Duplicated definition for: 'collectionElements'
<Line 842, Column 48>: XML-24509: (Error) Duplicated definition for: 'list'
<Line 853, Column 47>: XML-24509: (Error) Duplicated definition for: 'set'
<Line 862, Column 41>: XML-24509: (Error) Duplicated definition for: 'map'
<Line 869, Column 45>: XML-24509: (Error) Duplicated definition for: 'entry'
<Line 877, Column 45>: XML-24509: (Error) Duplicated definition for: 'props'
<Line 886, Column 26>: XML-24509: (Error) Duplicated definition for: 'key'
<Line 897, Column 27>: XML-24509: (Error) Duplicated definition for: 'prop'
<Line 916, Column 39>: XML-24509: (Error) Duplicated definition for: 'propertyType'
<Line 960, Column 45>: XML-24509: (Error) Duplicated definition for: 'baseCollectionType'
<Line 971, Column 46>: XML-24509: (Error) Duplicated definition for: 'typedCollectionType'
<Line 987, Column 34>: XML-24509: (Error) Duplicated definition for: 'mapType'
<Line 1008, Column 36>: XML-24509: (Error) Duplicated definition for: 'entryType'
<Line 1047, Column 40>: XML-24509: (Error) Duplicated definition for: 'listOrSetType'
<Line 1056, Column 36>: XML-24509: (Error) Duplicated definition for: 'propsType'
<Line 1069, Column 45>: XML-24509: (Error) Duplicated definition for: 'defaultable-boolean'
ERROR org.springframework.web.servlet.FrameworkServlet(229) - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Line 10 in XML document from class path resource [spring/servlet/sellitem-webflow-config.xml] is invalid; nested exception is oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
Caused by:
oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
 at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:431)
 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:290)
 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:287)
 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:181)
 at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:151)
 at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:77)
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:405)
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:357)
 at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
 at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:126)
 at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:142)
 at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:123)
 at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:91)
 at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:94)
 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:294)
 at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
 at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:308)
 at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:252)
 at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:221)
 at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:115)
 at javax.servlet.GenericServlet.init(GenericServlet.java:211)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
 at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 at java.lang.Thread.run(Unknown Source)
So it seems like these JARs are incompatible with each other. Is there any way I can use the Oracle DocumentBuilder for my XML Publisher classes and the xerces for the rest of the app?
Thanks,
Leo Hart

Now one has any advice? :(

FCPX XML not exporting audio with project...

FCPX XML not exporting audio with any project.
I have tried with several different projects to no avail.
Any thoughts or suggestions?
Thanks

I used no special setting. I even tried to just export audio. Still no audio. I checked the file with GSpot, it shows that it has audio.
Then I though I just went ahead an encode this and output to DVD as a test. It is indeed still no audio when playback on home dvd player.

UNICODE System - XML Encoding Error

Dear Experts,
We've upgraded our SAP system to ECC 6.0 Unicode. One of our applications works with XML files and we've been experimenting some problems with the XML encoding since the machine is Unicode enabled. In the XML structure we obtain strange chinesse characters:
This should be the right xml response:
<?xml version="1.0" encoding="utf-8"?><OpenHR><employee><id>69900004</id><name>Employee 1, Romania</name><orgName>Test ROMANIA</orgName><role>EMPLOYEE</role><flex>NO</flex><company>NE</company></employee><labels><label id="delegation">Delegations</label>
We obtain:
⸰㰿硭氠癥牳楯渽∱⸰u2220敮捯摩湧㴢畴昭㠢㼾㱏灥湈刾㱥浰汯祥放㱩搾㘹㤰〰〴㰯楤㸼湡浥㹅浰汯祥攠ㄬ⁒潭慮楡㰯湡浥㸼潲李慭放呥獴⁒位䅎䥁㰯潲李慭放㱲潬放䕍偌余䕅㰯牯汥㸼晬數㹎似⽦汥砾㱣潭灡湹㹎䕏㰯捯浰慮社㰯敭灬潹敥㸼污扥汳㸼污扥氠楤㴢摥汥条瑩潮∾䑥汥条瑩潮猼⽬慢敬㸼污扥氠楤㴢桥汰∾䡥汰㰯污扥氾㱬慢敬⁩搽≩湣楤敮捥獔楴汥∾健牳潮湥氠䅤浩湩獴牡瑩潮㰯污扥氾㱬慢敬⁩搽≮潄敬敧慴楯渢㹐汥慳攬⁲整畲渠瑯睮慬敮摡爠楦⁹潵⁷慮琠瑯捣敳猠瑯⁤敬敧慴楯湳㰯污扥氾㱬慢敬⁩搽≮潴敃潮晩牭兵敳瑩潮∾偲敳猠慣捥灴⁩映祯甠獨潵汤⁧整⁩琼
Here is the code where we guess the problem is (we have tried with differente encoding types: ISO-8859-1, UTF-8, UTF-16 and DEFAULT).
DATA: S_ENCODING_TYPE TYPE STRING,
 ENCODING TYPE REF TO IF_IXML_ENCODING.
S_ENCODING_TYPE = 'iso-8859-1'.
ENCODING = IXML->CREATE_ENCODING( CHARACTER_SET = S_ENCODING_TYPE
 BYTE_ORDER = 0 ).
CALL METHOD ODOCUMENT->SET_ENCODING
 EXPORTING ENCODING = ENCODING.
CALL FUNCTION 'SDIXML_DOM_TO_XML'
 EXPORTING
 DOCUMENT = ODOCUMENT
 IMPORTING
 SIZE = ISIZERAW
 TABLES
 XML_AS_TABLE = IDATA
 EXCEPTIONS
 NO_DOCUMENT = 1
 OTHERS = 2.
(IDATA is the variable where we see the chinesse text)

It will not give you any effect to set up encoding because this function module sets its own encoding inside:
encoding = pixml->create_encoding( character_set = 'UTF-8' byte_order = 0 ).
Renderer is created by the kernel:
by kernel module abkm_iXML_CreateRenderer.
Something may be wrong with the installation.

Creating XML-files in ABAP with format ISO-8859-1 after the use of unicode

Hello,
We have a problem with XML-files created in z_abap-programma.
Before the use of unicode the XML-file was of the format: ISO-8859-1.
After the introducting of unicode the format is UTF-16.
In the abap-program we are using:
        CALL TRANSFORMATION xls-program
         SOURCE t_vbak = it_vbak
         RESULT XML xmlstring.
        CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
          EXPORTING
            text     = xmlstring
          IMPORTING
            buffer   = lx_xml_as_string.
        CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
          EXPORTING
            buffer        = lx_xml_as_string
          IMPORTING
            output_length = li_xml_size
          TABLES
            binary_tab    = ltb_xml_table.
        CALL METHOD cl_gui_frontend_services=>gui_download
          EXPORTING
            bin_filesize = li_xml_size
            filename     = lc_filename
            filetype     = 'BIN'
          CHANGING
            data_tab     = ltb_xml_table
          EXCEPTIONS
            OTHERS       = 24.
Is it prossible to create the XML-file with the format ISO-8859-1 after the unicode, please can you explane how to solve this problem.
Regards,
Theo Pijlman

hi theo,
did you read my thread i wrote some days before ? have a look in my sample coding find   " if_ixml_encoding ..... " there you can set the encoding of character .
greetz
tony
thread:
Re: abap to xml
SAP Explanation for Interface if_ixml_encoding :
http://help.sap.com/saphelp_nw04/helpdata/de/bb/5766a6dca511d4990b00508b6b8b11/content.htm

Set XML encoding by saving with Xerces

Similar Messages

Maybe you are looking for