My Oracle Support Banner

AsFile Encoded XML Special Characters Are Stored Unencoded (Doc ID 1402800.1)

Last updated on SEPTEMBER 13, 2019

Applies to:

Oracle Insurance Policy Administration J2EE - Version 7.0 and later
Information in this document applies to any platform.


Portions of text that the user imports via the AsFile webservice, are stored in the table AsActivityField with HTML characters that were encoded in the original message, unencoded. This means that when OIPA later renders that AsActivityField text in a web browser (i.e. in HTML format), the display is "broken".

For example, the string "< 20" looks like these seven ASCII characters, when encoded: &lt; 20

During JIBX mapping, which takes the customer's transformed input XML and maps the OIPA business objects in XML format, into Java class instances, these are unencoded back to the string: "< 20", which is then stored as is in AsActivityField. Since '<' is a special character in HTML, a string that contains it is not displayed properly when rendered into HTML.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.