My Oracle Support Banner

ALSB 3.0 - Convert non-printable characters to invalid XML elements in Tuxedo Transport (Doc ID 984222.1)

Last updated on APRIL 14, 2021

Applies to:

Oracle Service Bus - Version 2.6.1RP and later
Information in this document applies to any platform.

Symptoms

Non-printable characters are stored in char fields that get converted into
non-valid XML elements by the WTC/Tux transport.

When non-printable low-range characters are used in FML32 char buffers, the
Tuxedo Transport does not produce valid XML. 

Sometimes C developers use char fields to store integers instead of char
values to save space. Tux transport tries to translate those values into
their decimal representation, which in some cases are not valid XML elements.

Non-valid XML elements make an XML document non-valid, making it imposible to be
used by ALSB proxies in XQueries and other manipulations.

Cause

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
Symptoms
Cause
Solution
References


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