The connector has been globalized so that it can support double-byte character sets. When the connector transfers data from a location that uses one character code to a location that uses a different code set, it performs character conversion to preserves the meaning of the data.
The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encodings for characters in most known character code sets (both single-byte and multibyte). Most components in the WebSphere business integration system are written in Java. Therefore, when data is transferred between most integration components, there is no need for character conversion.
This section discusses localization and the connector.
The connector uses pluggable protocol listeners for event notification. The protocol listeners extract the SOAP message from the transport and invoke the SOAP data handler. This section describes how each of the listeners encode SOAP messages over the transport:
The connector uses pluggable protocol handlers for request processing. The protocol handlers invoke the SOAP data handler. This section describes how each of the handlers encodes SOAP message over the transport:
This section discusses localization and the SOAP data handler.
XML element names and attributes names must be legal ascii characters that are allowed by either business object names, business object attribute names or business object application-specific information.
Internationalized characters are not supported in business object names or business object attribute names. Only attribute values can be internationalized.
When transforming a SOAP message into a business object, the data handler can receive a string only. The data handler simply populates the business object with string values and returns the business object. Java strings are UCS2, and therefore double-byte enabled characters are transferred without problem. Only XML element and attribute values can be non-ascii characters (see character limitations). When transforming a business object to a SOAP message, the data handler uses the Xerces parser to convert a business object to a string. Java strings are UCS2, so double-byte enabled characters are transferred without problem. Only XML element and attribute values can be non-ascii characters (see character limitations).
This section discusses localization and the WSDL ODA.
The WSDL ODA does not support characters other than legal ASCII in the WSDL file. The WSDL ODA can support file names and URLs in other character sets. But the contents of these files must be in legal ASCII.
Properties in the Configuring Agent table of the WSDL ODA are globalized as follows: