Unescaping XML entity references within a stored procedure invoked from the Database Adapter
Last updated on APRIL 15, 2016
Applies to:Oracle SOA Suite - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
A Database Adapter used by a SOA composite invokes a stored procedure, providing an XML payload as the input parameter.
In the stored procedure, when extracting data from the XML payload, it is found that any entity references within the XML have been escaped.
eg. An "&" ampersand character in the XML will have been escaped to "&"
However the requirement is to have the characters stored in the database in their original un-escaped form.
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