XML processing behavior change

In previous versions, the system did a dynamic encoding conversion during XML-to-XML translation if the encoding was changed by modifying ?xml.&encoding. This conversion no longer happens because all is internally normalized to Unicode.

Upgraded protocol threads default to binary encoding so that there is no conversion in the threads. This can result in different behavior for sites that use an XML-to-XML translation where the encoding is altered in translation.

You can compensate for this behavior change by specifying XML encoding mode for the inbound and outbound threads in this type of interface. This must be performed manually. You can use a utility script that looks for translate files that have XML as the input and output format. It can then find NetConfig routes that invoke these translations. You could then choose what action to take. This type of utility is considered desirable, but not a requirement.