Encoded attribute

Hi folks
I have a Access Manager Installation (2005Q1) This server have an option for password reset. in this option you have to answer the questions to reset your password, I have to change the question and answer for several users, I'm trying to use ldapmopdify to change this encoded value but ldapmodify do not encode the value just put it in clear text.
The attribute is iplanet-am-user-password-reset-question-answer and this is a example of the ldif syntax:
iplanet-am-user-password-reset-question-answer: AQICfd3g1d11ZlT9YfoW0SDPCy4J9R7ZyywoIwnE/qe+L10uwVrS15KWog==
This is an example of my ldif file to use with ldapmodify
dn: uid=one,ou=People,dc=my,dc=domain,dc=com
changetype: modify
replace: iplanet-am-user-password-reset-question-answer
iplanet-am-user-password-reset-question-answer: question one answer one
and the comand line is:
ldapmodify -D "cn=Directory Manager" -w solaris123 -f file.ldif
Do somebody know how can i change the value for this encoded attribute using ldapmodify????

hi...
any body can help me on my case study?
pls. give me program/code on java about CALENDAR & BORROWING MORTAGAGES....???? pls... badly needed...ASAP..
thanks...godbless!!!!

Similar Messages

File Adapter receiver channel : change encoding attribut in xml file

Hi,
How can I change the XML encoding attribut
from:
<?xml version="1.0" encoding="UFT-8"?>
to:
<?xml version="1.0" encoding="ISO-8859-1"?>
in my File Adapter, receiver channel ?

Hi,
plz chk the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
●      Select the File Type of the document:
○       Binary
○       Text
Under File Encoding, specify a code page.
The default setting is to use the system code page that is specific to the configuration of the installed operating system.
The content of the message is converted to the corresponding code page before the message is saved as a file.
Permitted values for the code page are the existing Charsets of the Java runtime. According to the SUN specification for the Java runtime, at least the following standard character sets must be supported:
Regards

How to generate the encoding attribute

Hi,
After reading a lot of posts on this forum and trying out suggestions on both 9.2 and 10G databases my question is stil unanswered. So I thought I'd ask my question again.
Original post is here (dbms_xmlgen how to generate encoding attribute
I'm currently generating XML using the dbms_xml packages. But same problem exists when using sql/xml functions.
I get this header :
<?xml version="1.0"?>
My database has the WE8MSWIN1252 characterset. So I want the header to be:
<?xml version="1.0" encoding="windows-1252"?>
My question is how can I generate the xml header automatically, depending on the database characterset?
The code has to work on 9.2 and 10G. I see 2 possible solutions.
1 The encoding attribute value is generated automatically
2 I generate it myself but then I need a to translate the database characterset name to the proper value for the encoding attribute value.
Rene

You could write (indeed as you mentioned option in 2) your own, for instance, as shown here:
Re: Concatenation, Attributes, and Processing Instruction
and/or use XMLROOT
but that said, you can't use XMLROOT in 9.2 yet.
but based on your requirements it is not easy / a lot of work to do, although I wonder what you are trying to achieve and don't forget that if you pick the database characterset you will probably overrule situations based on:
(http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch3globenv.htm#i1006415)
NLS_SESSION_PARAMETERS shows the NLS parameters and their values for the session that is querying the view. It does not show information about the character set.
NLS_INSTANCE_PARAMETERS shows the current NLS instance parameters that have been explicitly set and the values of the NLS instance parameters.
NLS_DATABASE_PARAMETERS shows the values of the NLS parameters for the database. The values are stored in the database.
or in other words if NLS settings are manually changed within a session, instance or database context.
Message was edited by:
Marco Gralike

Dbms_xmlgen how to generate encoding attribute

HI, I'm generating XML using the dbms_xml packages. It generates this header
<?xml version="1.0"?> My database has the WE8MSWIN1252 characterset. So I want the header to be:
<?xml version="1.0" encoding="windows-1252"?>My question is how can I generate the xml header automatically, depending on the databases character encoding settings?
Rene

You could write (indeed as you mentioned option in 2) your own, for instance, as shown here:
Re: Concatenation, Attributes, and Processing Instruction
and/or use XMLROOT
but that said, you can't use XMLROOT in 9.2 yet.
but based on your requirements it is not easy / a lot of work to do, although I wonder what you are trying to achieve and don't forget that if you pick the database characterset you will probably overrule situations based on:
(http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch3globenv.htm#i1006415)
NLS_SESSION_PARAMETERS shows the NLS parameters and their values for the session that is querying the view. It does not show information about the character set.
NLS_INSTANCE_PARAMETERS shows the current NLS instance parameters that have been explicitly set and the values of the NLS instance parameters.
NLS_DATABASE_PARAMETERS shows the values of the NLS parameters for the database. The values are stored in the database.
or in other words if NLS settings are manually changed within a session, instance or database context.
Message was edited by:
Marco Gralike

Data Set - Encode Attribute Value?

I'm using an HTML data set with an active region. Some of the
data is to be used as attribute values (e.g. as the "value" of an
"input" tag), and some of the data is to be used within the HTML of
the document (but should not be rendered as HTML). What is the best
way (recommended practice) for encoding the data for these uses? In
other words, does the spry framework provide such utilities? Is
there a way to pull the data out of the data set already encoded
for use as an attribute value? Or with >, <, and &
properly encoded for use in HTML?

I guess you are also using SpryData.js in the same page.
SpryData.js has a function called
Spry.Utils.encodeEntities(string);
It will encode your Entities for you and returns the changed
string. If you data is already encoded before you brought it in to
the SpryDataset, make sure you didnt set the columnType to html.
If not you can do something like this
<script type="text/javascript">
function encodeEntities(region, lookupFunc)
return
Spry.Utils.encodeEntities(lookupFunc("{dsProducts::desc}"));
</script>
<div spry:region="dsProducts">
<ul spry:repeatchildren="dsProducts">
<li>{name} - {function::encodeEntities}</li>
</ul>
</div>

Changing the encoding attribute in xml output

We are creating an xml file using:
vc_string_clob := dbms_xmlgen.getxml('select * from mytable');
then opening the file with UTL_FILE.FOPEN('dir','filename','W',31767)
then parsing through vc_string_clob and using UTL_FILE.PUT_LINE to write to the file.
This all works fine, expect the header of the XML file is <?xml version="1.0"?> and our users need it to be <?xml version="1.0" encoding="ISO-8859-1"?>
Is there a function within dbms_xmlgen that will allow me to change this?
I'm thinking I can use brute force to change it, but I'm sure there is a 'more correct' way to go about it.
Thank you,
Jill Jacomine

Hi Jill,
Welcome to the forum.
There are easier methods to output XML to a file, rather than using line-by-line UTL_FILE operations.
For example :
DECLARE
xml_result xmltype;
doc        dbms_xmldom.DOMDocument;
BEGIN
xml_result := dbms_xmlgen.getXMLType('SELECT * FROM scott.dept');
doc := dbms_xmldom.newDOMDocument(xml_result);
dbms_xmldom.writeToFile(doc, 'TEST_DIR/my_file.xml', 'ISO-8859-1');
dbms_xmldom.freeDocument(doc);
END;
/or,
DECLARE
xml_result xmltype;
xml_prolog clob := '<?xml version="1.0" encoding="ISO-8859-1"?>'||chr(10);
BEGIN
xml_result := dbms_xmlgen.getXMLType('SELECT * FROM scott.dept');
dbms_xslprocessor.clob2file(xml_prolog || xml_result.getClobVal(), 'TEST_DIR', 'my_file.xml');
END;
/Both will produce :
<?xml version="1.0" encoding="ISO-8859-1"?>
<ROWSET>
<ROW>
    <DEPTNO>10</DEPTNO>
    <DNAME>ACCOUNTING</DNAME>
    <LOC>NEW YORK</LOC>
</ROW>
<ROW>
    <DEPTNO>20</DEPTNO>
    <DNAME>RESEARCH</DNAME>
    <LOC>DALLAS</LOC>
</ROW>
<ROW>
    <DEPTNO>30</DEPTNO>
    <DNAME>SALES</DNAME>
    <LOC>CHICAGO</LOC>
</ROW>
<ROW>
    <DEPTNO>40</DEPTNO>
    <DNAME>OPERATIONS</DNAME>
    <LOC>BOSTON</LOC>
</ROW>
</ROWSET>Hope that helps.

XML encoding attribute

Hello,
I am using Oracle 10.1.0.5.0 and trying to generate XML with PL/SQL by using XMLGEN package getXML function.
The result I get is almost what I want, only one slight problem in XML header.
XML header in resul is: <?xml versio = "1.0"?>
How can I get the result header like this: <?xml versio = "1.0" encoding = "UTF-8"?>

Use DBMS_XMLQuery.
We have got a method named 'setEncodingTag' in DBMS_XMLQuery package, using which u can set the encoding.

Node doesn't belong to the current document and Invalid UTF8 encoding errors

Hi
I'm creating a XSQL page that calls a PL/SQL procedure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<page xmlns:xsql="urn:oracle-xsql" connection="sgvrt">
<xsql:include-owa>xml_indicadores_epm;</xsql:include-owa>
</page>
When I run the page I get:
Node doesn't belong to the current document.
if I use "<include-xml>" I get the following error:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<page>
<xsql-error action="xsql:include-xml">
<message>Invalid UTF8 encoding.</message>
</xsql-error>
</page>
The XML page generated is well formed and it sends "test/xml; charset="ISO-8859-1" myme type. I test it in IE and it runs fine. I wrote a simple procedure that generates a simple one tag XML file and I still get the same errors.

Thanks for the reply
We've tried using the encoding attribute (encoding="ISO-8859-1") but it generates the same errors. We're using XSQL that comes with 9iAS 1.0.2.2.2a. We also tried with XSQL that comes with Oracle 9.2.0. It seems that the parser is not detecting if the XML document has a different encoding than UTF8.

Node doesn't belong to the current document and Invalid UTF8 encoding.

Hi
I'm creating a XSQL page that calls a PL/SQL procedure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<page xmlns:xsql="urn:oracle-xsql" connection="sgvrt">
<xsql:include-owa>xml_indicadores_epm;</xsql:include-owa>
</page>
When I run the page I get:
Node doesn't belong to the current document.
if I use "<include-xml>" I get the following error:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<page>
<xsql-error action="xsql:include-xml">
<message>Invalid UTF8 encoding.</message>
</xsql-error>
</page>
The XML page generated is well formed and it sends "test/xml; charset="ISO-8859-1" myme type. I test it in IE and it runs fine. I wrote a simple procedure that generates a simple one tag XML file and I still get the same errors.
The page generated by the PL/SQL procedure is:
<indicadores_gestion_epm>
<fecha>Junio 2001</fecha>
<indicador><descripcion>Costo de Generacisn de Potencial por Perforacisn (Conv.)</descripcion><plan_valor>N/D</plan_valor><real_valor>48,21</real_valor><unidad_medida>M$/Bl</unidad_medida></indicador>
<indicador><descripcion>Costo de Generacisn de Potencial por Perforacisn (GD)</descripcion><plan_valor>N/D</plan_valor><real_valor>0</real_valor><unidad_medida>M$/Bl</unidad_medida></indicador>
<indicador><descripcion>Costo de Exploracion Aqo Actual (GD)</descripcion><plan_valor>N/D</plan_valor><real_valor>22,48</real_valor><unidad_medida>$/BPE</unidad_medida></indicador>
<indicador><descripcion>Costo de Exploracion Promedio (GD)</descripcion><plan_valor>N/D</plan_valor><real_valor>19,98</real_valor><unidad_medida>$/BD</unidad_medida></indicador>
<indicador><descripcion>Incorporacion de Reservas Probadas y Probables de Crudo (GD)</descripcion><plan_valor>647</plan_valor><real_valor>2</real_valor><unidad_medida>MMBLs</unidad_medida></indicador>
<indicador><descripcion>Incorporacion de Reservas Probadas y Probables Gas (GD)</descripcion><plan_valor>N/D</plan_valor><real_valor>4</real_valor><unidad_medida>MMMPC</unidad_medida></indicador>
<indicador><descripcion>Contribuciones a las Reservas Probadas de Gas (GD)</descripcion><plan_valor>N/D</plan_valor><real_valor>5</real_valor><unidad_medida>MMMPC</unidad_medida></indicador>
<indicador><descripcion>Produccion Disponible Promedio de Crudo (GD)</descripcion><plan_valor>362,8</plan_valor><real_valor>1401,66</real_valor><unidad_medida>MBD</unidad_medida></indicador>
<indicador><descripcion>Capacidad de Produccisn de Crudo</descripcion><plan_valor>N/D</plan_valor><real_valor>0</real_valor><unidad_medida>MBD</unidad_medida></indicador>
<indicador><descripcion>Contribuciones a las Reservas Probadas de Crudo (GD)</descripcion><plan_valor>1750</plan_valor><real_valor>1750</real_valor><unidad_medida>MMBLs</unidad_medida></indicador>
<indicador><descripcion>Costo Unitario de Operacisn (Conv.)</descripcion><plan_valor>0</plan_valor><real_valor>,01</real_valor><unidad_medida>$/BL</unidad_medida></indicador>
<indicador><descripcion>Costo Unitario de Operacisn (GD)</descripcion><plan_valor>N/D</plan_valor><real_valor>102,53</real_valor><unidad_medida>$/BL</unidad_medida></indicador>
<indicador><descripcion>Disponibilidad de Gas (Acumulado)</descripcion><plan_valor>N/D</plan_valor><real_valor>0</real_valor><unidad_medida>MMPCD</unidad_medida></indicador>
<indicador><descripcion>Produccion de Crudo Entregada a RSC Promedio</descripcion><plan_valor>N/D</plan_valor><real_valor>0</real_valor><unidad_medida>MBD</unidad_medida></indicador>
<indicador><descripcion>Costo de Generacion de Potenc. RA/RC (Conv.)</descripcion><plan_valor>N/D</plan_valor><real_valor>3,15</real_valor><unidad_medida>M$/BD</unidad_medida></indicador>
<indicador><descripcion>Costo de Generacion de Potenc. RA/RC (GD)</descripcion><plan_valor>N/D</plan_valor><real_valor>0</real_valor><unidad_medida>M$/BD</unidad_medida></indicador>
</indicadores_gestion_epm>

Thanks for the reply
We've tried using the encoding attribute (encoding="ISO-8859-1") but it generates the same errors. We're using XSQL that comes with 9iAS 1.0.2.2.2a. We also tried with XSQL that comes with Oracle 9.2.0. It seems that the parser is not detecting if the XML document has a different encoding than UTF8.

How to change encoding in output txt file

Hello All,
I use Oracle 10g, database characterset is UTF8. I've got a txt file with corresponding UTF8, could I change a characterset of the txt output file for the other one - ANSI, for example?
Thanks in advance for your help!
Best regards,
Tany

I haven't tried this .. but I think you can provide the encoding attribute to the xsl:output element. See the link for more details :
http://www.w3.org/TR/xslt#output
HTH
Rahul

Problems with reading XML files with ISO-8859-1 encoding

Hi!
I try to read a RSS file. The script below works with XML files with UTF-8 encoding but not ISO-8859-1. How to fix so it work with booth?
Here's the code:
import java.io.File;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import java.net.*;
* @author gustav
public class RSSDocument {
    /** Creates a new instance of RSSDocument */
    public RSSDocument(String inurl) {
        String url = new String(inurl);
        try{
            DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
            Document doc = builder.parse(url);
            NodeList nodes = doc.getElementsByTagName("item");
            for (int i = 0; i < nodes.getLength(); i++) {
                Element element = (Element) nodes.item(i);
                NodeList title = element.getElementsByTagName("title");
                Element line = (Element) title.item(0);
                System.out.println("Title: " + getCharacterDataFromElement(line));
                NodeList des = element.getElementsByTagName("description");
                line = (Element) des.item(0);
                System.out.println("Des: " + getCharacterDataFromElement(line));
        } catch (Exception e) {
            e.printStackTrace();
    public String getCharacterDataFromElement(Element e) {
        Node child = e.getFirstChild();
        if (child instanceof CharacterData) {
            CharacterData cd = (CharacterData) child;
            return cd.getData();
        return "?";
}And here's the error message:
org.xml.sax.SAXParseException: Teckenkonverteringsfel: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (radnumret kan vara f�r l�gt).
    at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
    at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
    at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
    at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
    at getrss.RSSDocument.<init>(RSSDocument.java:25)
    at getrss.Main.main(Main.java:25)

I read files from the web, but there is a XML tag
with the encoding attribute in the RSS file.If you are quite sure that you have an encoding attribute set to ISO-8859-1 then I expect that your RSS file has non-ISO-8859-1 character though I thought all bytes -128 to 127 were valid ISO-8859-1 characters!
Many years ago I had a problem with an XML file with invalid characters. I wrote a simple filter (using FilterInputStream) that made sure that all the byes it processed were ASCII. My problem turned out to be characters with value zero which the Microsoft XML parser failed to process. It put the parser in an infinite loop!
In the filter, as each byte is read you could write out the Hex value. That way you should be able to find the offending character(s).

RPC/SOAP-Encoded Web Service with Workshop

Is there anyway to create a RPC/SOAP-Encoded Web Service with Workshop ? There is an "encoding" attribute in the autotype ant task but no corresponding properties in Workshop.

Hi,
Thanks for the reference.
I have checked both in the wsdl and the Soap message,
rpc property effectively means rpc/encoded. Now that
would say that RPC/Literal is not supported ?
Here are what the messages looks like with rpc and
document properties
Thanks all for making this clear.
document wlw property = Document/Literal
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<ns:getEmployeeResult xmlns:ns="http://www.openuri.org/">
<ns:Address xmlns:ns="http://www.openuri.org/">
<ns:City xmlns:ns="http://www.openuri.org/">Luxembourg</ns:City>
<ns:Country xmlns:ns="http://www.openuri.org/">LU</ns:Country>
<ns:Number xmlns:ns="http://www.openuri.org/">2</ns:Number>
<ns:PostCode xmlns:ns="http://www.openuri.org/">1000</ns:PostCode>
<ns:Street xmlns:ns="http://www.openuri.org/">Bld. Royal</ns:Street>
</ns:Address>
<ns:Age xmlns:ns="http://www.openuri.org/">20</ns:Age>
<ns:Name xmlns:ns="http://www.openuri.org/">Dupont</ns:Name>
<ns:FirstNames xmlns:ns="http://www.openuri.org/">
<ns:String xmlns:ns="http://www.openuri.org/">Jean</ns:String>
<ns:String xmlns:ns="http://www.openuri.org/">Jacques</ns:String>
</ns:FirstNames>
</ns:getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
rpc wlw property = RPC/Soap-Encoded
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
<getEmployeeResult xmlns:s="http://www.openuri.org/encodedTypes" xsi:type="s:Employee">
<Address xsi:type="s:Address">
<City xsi:type="xsd:string">Luxembourg</City>
<Country xsi:type="xsd:string">LU</Country>
<Number xsi:type="xsd:int">2</Number>
<PostCode xsi:type="xsd:string">1000</PostCode>
<Street xsi:type="xsd:string">Bld. Royal</Street>
</Address>
<Age xsi:type="xsd:int">20</Age>
<Name xsi:type="xsd:string">Dupont</Name>
<FirstNames SOAP-ENC:arrayType="xsd:string[2]" xsi:type="SOAP-ENC:Array">
<String xsi:type="xsd:string">Jean</String>
<String xsi:type="xsd:string">Jacques</String>
</FirstNames>
</getEmployeeResult>
</ns:getEmployeeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Message was edited by phcollignon at Aug 27, 2004 2:54 AM

Encoding error with xerces/JDOM

hej,
We have XML files that must be encoded in ISO-8859-1(i.e.encoding attribute in the document's XML declaration) to handle swedish characters. When trying to read in the XML document via JDOM (default parse is xerces) the following error is thrown:
Error message : Unable to build document (url). Invalid byte 2 of 3-byte UTF-8 sequence.
java.lang.RuntimeException: Unable to build document (url). Invalid byte 2 of 3-byte UTF-8 sequence.
at se.sfa.rfv.sat.installation.XMLFacade.build(XMLFacade.java:398)
at se.sfa.rfv.sat.installation.XMLFacade.main(XMLFacade.java:458)
If we transform the URL into an InputStream then transform the character encoding to UTF-8 likely the swedish characters (�,�, and �) will be removed. Not happening.
Is there are way to tell the underlying parser that the incoming data stream is encoded as ISO-8859-1 and build the document? Must be.
/ Matthew Young

Trying to use the transformer class to translate to ISO-8859-1 encoding but the following code hangs at the transform stage:
         InputStream inputstream = url.openConnection().getInputStream();
         StreamSource source = new StreamSource(inputstream);
         PipedWriter pipedwriter = new PipedWriter();
         PipedReader pipereader = new PipedReader(pipedwriter);
         PrintWriter printwriter = new PrintWriter(pipedwriter);
         StreamResult result = new StreamResult(printwriter);
         TransformerFactory factory = TransformerFactory.newInstance();
         Transformer transformer = factory.newTransformer();
         transformer.setOutputProperty(OutputKeys.ENCODING, "ISO-8859-1");
         transformer.transform(source, result);
         this.document = builder.build(pipereader);The URL passed in is the url to the input XML file. Assume the problem is related to the piping IO streams. Any ideas? / Matthew

XMLReader throws "Invalid UTF8 encoding." - Need parser for ISO-8859-1 chrs

Hi,
We are facing an issue when we try to send data which is encoded in "ISO-8859-1" charset (german chars) via the EMDClient (agent), which tries to parse it using the oracle.xml.parser.v2.XMLParser . The parser, while trying to read it, is unable to determine the charset encoding of our data and assumes that the encoding is "UTF-8", and when it tries to read it, throws the :
"java.io.UTFDataFormatException: Invalid UTF8 encoding." exception.
I looked at the XMLReader's code and found that it tries to read the first 4 bytes (Byte Order Mark - BOM) to determine the encoding. It is probably expecting us to send the data where the first line is probably:
<?xml version="1.0" encoding="iso88591" ?>
But, the data that our application sends is typically as below:
========================================================
# listener.ora Network Configuration File: /ade/vivsharm_emsa2/oracle/work/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = semsa2)
(ORACLE_HOME = /ade/vivsharm_emsa2/oracle)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = tcp)(HOST = stadm18.us.oracle.com)(PORT = 15100))
========================================================
the first 4 bytes in our case will be, int[] {35, 32, 108, 105} == chars {#, SPACE, l, i},
which does not match any of the encodings predefined in oracle.xml.parser.v2.XMLReader.pushXMLReader() method.
How do we ensure that the parser identifies the encoding properly and instantiates the correct parser for "ISO-8859-1"...
Should we just add the line <?xml version="1.0" encoding="iso88591" ?> at the beginning of our data?
We have tried constructing the inputstream (ByteArrayInputStream) by using String.getBytes("ISO-8859-1") and passing that to the parser, but that does not seem to work.
Please suggest.
Thanks & Regards,
Vivek.
PS: The exception we get is as below:
java.io.UTFDataFormatException: Invalid UTF8 encoding.
at oracle.xml.parser.v2.XMLUTF8Reader.checkUTF8Byte(XMLUTF8Reader.java:160)
at oracle.xml.parser.v2.XMLUTF8Reader.readUTF8Char(XMLUTF8Reader.java:187)
at oracle.xml.parser.v2.XMLUTF8Reader.fillBuffer(XMLUTF8Reader.java:120)
at oracle.xml.parser.v2.XMLByteReader.saveBuffer(XMLByteReader.java:450)
at oracle.xml.parser.v2.XMLReader.fillBuffer(XMLReader.java:2229)
at oracle.xml.parser.v2.XMLReader.tryRead(XMLReader.java:994)
at oracle.xml.parser.v2.XMLReader.scanXMLDecl(XMLReader.java:2788)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:502)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:205)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:180)
at org.xml.sax.helpers.ParserAdapter.parse(ParserAdapter.java:431)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.readXML(RemoteOperationInputStream.java:363)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.readHeader(RemoteOperationInputStream.java:195)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.read(RemoteOperationInputStream.java:151)
at oracle.sysman.emSDK.emd.comm.EMDClient.remotePut(EMDClient.java:2075)
at oracle.sysman.emo.net.util.agent.Operation.saveFile(Operation.java:758)
at oracle.sysman.emo.net.common.WebIOHandler.saveFile(WebIOHandler.java:152)
at oracle.sysman.emo.net.common.BaseWebConfigContext.saveConfig(BaseWebConfigContext.java:505)

Vivek
Your message is not XML. I believe that the XMLParser is going to have problems with that as well. Perhaps you could wrap the message in an XML tag set and begin the document as you suggested with <?xml version="1.0" encoding="iso88591"?>.
You are correct in that the parser uses only the first 4 bytes to detect the encoding of the document. It can only determine if the document in ASCII or EPCDIC based. If it is ASCII it can detect only between UTF-8 and UTF-16. It will need the encoding attribute to recognize the ISO-8859-1 encoding.
hope this helps
tom

Invalid UTF8 encoding & XSU

I am using XSU version 1.2.
to generating an XML document from data
which contains German (d,|,v).
The XML parser (2) cannot handle this.
The error i get is:
ERROR at line 1:
ORA-20100: Error occurred while parsing: Invalid UTF8 encoding.
ORA-06512: at "XML.XMLPARSER", line 22
ORA-06512: at "XML.XMLPARSER", line 93
Others seem to have had this problem also,
but i couldn't see the solution...
Thank you
Sonal
null

The Document must contain
encoding = "ISO-8859-1" in the ?xml tag.
How can i make the XMLGEN.getxml create a document contaning the encoding attribute ?
Thank you
Sonal
null

Encoded attribute

Similar Messages

Maybe you are looking for