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: 11.1.1.2.0 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

This note discusses the issue and solution for: TranslateToNative ( XPath Extension Function) when used in a BPEL Process does not consistently add required padding to empty strings.

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:

<outputVariable>
 <part name="payload">
  <processResponse>
   <resultAssign/>
     <resultXSLTText>000000000</resultXSLTText>
   </processResponse>
 </part>
</outputVariable>


Output when a string "a" was assigned to the variable:

<outputVariable>
 <part name="payload">
  <processResponse>
   <resultAssign>00000000a</resultAssign>
   <resultXSLTText>000000000</resultXSLTText>
  </processResponse>
 </part>
</outputVariable>

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.

Cause

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