Invalid Xml For Ampersand Character In Bpel Email Attachment
(Doc ID 1336946.1)
Last updated on MARCH 30, 2019
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.3.4 and later
Information in this document applies to any platform.
A BPEL process contains payload data in XML format which contain a correctly-formatted, i.e. escaped, ampersand character as & a m p ; (without blanks). Viewing the data in the BPEL instance's flow confirms that this character has been escaped correctly. If this same payload is sent as an email notification attachment, the ampersand character is replaced by an actual ampersand. I.e. it is converted from "& a m p ;" to a single "&". This is invalid XML, as defined in the XML specification at
See - Extensible Markup Language (XML) 1.1 (Second Edition)
under 2.4 Character Data and Markup - "The ampersand character (&) and the left angle bracket (<) MUST NOT appear in their literal form... etc."
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document