IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only

why utf-16 encoding throws error?

  • 1.  why utf-16 encoding throws error?

    Posted 11/13/07 05:33 AM

    Originally posted by: SystemAdmin


    Hi,
    This is a very basic question. While converting xsd to type tree,
    I am able to generate type tree for only the utf-8 encoding.For other encodings, i get errors like this. Why other encodings cannot be used?If can be used, how it can be done?

    A JAVA EXCEPTION HAS BEEN ENCOUNTERED DURING THE SCHEMA PARSING
    Schema parsing error - Line: 2, Column: 1
    JAVA EXCEPTION: Content is not allowed in prolog.
    CODE STACK:
    org.xml.sax.SAXParseException: Content is not allowed in prolog.
    + ...............+
    PARSE STACK:
    EMPTY OR NOT AVAILABLE

    ii)The map which was successful in windows client, is not running in mainframes. The same files were used in both environment, but no error was thrown in windows.

    the input file is like,

    <?xml version="1.0" encoding="utf-8"?><O2CInvoices>
    <FTP_INFO><SENDING_APP>CIS</SENDING_APP><SEQUENCE_NUMBER>3</
    <INVOICE><HEADER><SENDING_APP>CIS</SENDING_APP><SEQUENCE_NUM
    <LINE_ITEM><ACTIV_DESC>OC1</ACTIV_DESC><A_STATE_TAX>+0000001
    <SERIAL_NO><SERIAL_NO_DETAILS>KQ07YPT</SERIAL_NO_DETAILS></S
    </LINE_ITEM>

    It gives the following error,

    SAXParseException, Warning Ýline: 0 column: 0¨ An exception occurred! Type:Runti
    ntity could not be opened. Id=Test4.xsd
    Error (-1), "XMLParser: Input XML data is invalid."
    SAXParseException, Error Ýline: 1 column: 55¨ Unknown element 'O2CInvoices'
    ).
    Regards
    PriJag
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender