TranslateToNative (XPath Extension Function) Does Not Consistently Add Required Padding To Empty String
(Doc ID 1290555.1)
Last updated on MARCH 08, 2017
Applies to:Oracle SOA Platform - Version: 18.104.22.168.0
Information in this document applies to any platform.
TranslateToNative in some cases, when the variable used as a parameter to the TranslateToNative is initialized with an empty string using the assign activity does not work as expected and when initialized with an empty string using XSLT activity works as expected.
To better explain the issue, The expected behavior for TranslateToNative function for an empty string is to pad the empty string with 0s.
See the output of the test case:
Output when a empty string "" was assigned to the variable:
Output when a string "a" was assigned to the variable:
You would notice that when non empty string was passed to TranslateToNative function, it had padded the string with 0s where as with the empty string the padding did not occur.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|