Message Schema in UTF-16 Encoding Can Cause a Runtime Exception (Doc ID 1343745.1)

Last updated on SEPTEMBER 16, 2011

Applies to:

Oracle SOA Platform - Version: 11.1.1.5.0 to 11.1.1.5.0 - Release: 11gR1 to 11gR1
This problem can occur on any platform.

Symptoms

You may encounter the following runtime parsing error if a message schema is encoded in UTF-16.

Unable to parse schema <name>.xsd

Cause

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