Invalid Xml For Ampersand Character In Bpel Email Attachment (Doc ID 1336946.1)
Last updated on JULY 20, 2011
Oracle(R) BPEL Process Manager - Version: 10.1.3.4 to 126.96.36.199.0 - Release: AS10gR3 to 11gR1 This problem can occur on 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 http://www.w3.org/TR/xml11. 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."
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