IDOC-ETD Fails To Parse Unicode(e.g. UTF8)-IDOC Correctly
Last updated on NOVEMBER 03, 2016
Applies to:Sun Schema Runtime Environment (SRE) - Version 5.0.5u2 to 5.0.5u2 [Release 5.0]
Information in this document applies to any platform.
In SRE 5.0.5 Update 2 there are issues with IDOC Event Type Defintion (ETD)s when unmarshalling UTF-8 data. Even though the ETD's unmarshaller knows about the encoding that is the base of the array given to the unmarshaller's unmarshal(byte bytes) method, it fails to correctly parse a given Unicode-IDOC encoded as UTF-8.
When the IDOC is UTF-8 encoded, usual ASCII characters are using a single byte, while special characters use a 2-byte value. If the parser does not recognize that format, these characters are not properly parsed. One issue that might then occur is simply that the content of the parsed ETD does not fully reflect the content of the source IDOC. But since the size information is not properly calculated, it might also happen that unmarshal errors occur, e.g.
How is it possible to properly parse UTF-8 IDOCs?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms