Sunday, October 10, 2010

ora:parseEscapedXml function fails during conversion

The ora:parseEscapedXml functions fails to convert string which have & 'Ampersand' in them. It errors during conversion and the error in the BPEL Console is nowhere close to the issue. There has already a bug filed for this issue, bug# 5598150 and it appears to have been fixed in 11.1.1.0.0. I am running on 11.1.1.2.0 and I still face this issue !

On metalink, there is a workarouund provided for this issue. One needs to replace & with & amp; amp; (mentioned with spaces so that its not converted to & by html). This can be done using a XSLT replace all template or a java embedding node.

Refer to How to solve the Ora:Parseescapedxml error when you are using ampersand character [ID 418488.1] in metalink for the workaround using java.


Bug 5598150 - AMPERSAND ENTITY IS NOT HANDLED CORRECT




Peace!


Cheers,
-AR

1 comment:

Arun Ramesh said...

A new function from Oracle has been released - ora:parseXML(). This resolves the & issue.

Solution: Migrate the code from ora:parseEscapedXML() to ora:parseXML()


Metalink Note 1340195.1: https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=is1ahy3nn_4&_afrLoop=6484087315296

Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License