NonStop SOAP User's Manual

NonStop SOAP Features and Functions

NonStop SOAP User’s Manual—520501-012

4-30

Specifying the Server Encoding

NonStop SOAP 3.0 supports new server encodings, in addition to UTF-8. The new

encodings are supported only in the prebuilt SOAP servers (the servers that are

distributed in the <soapinstallation>/bin directory), and are not supported for SOAP

servers built using the generated code.

The tested output encodings are:

•

Shift_JIS

•

ISO-2022-JP

•

IBM1140(ebcdic)

Other encodings supported by the ICU library, and where the maximum character size

is 1 should also work.

NonStop SOAP does not support UTF-16 as the TS/MP server encoding.

Exposing DDL Fields as XML Attributes

In prior versions of NonStop SOAP each DDL field in a request/response definition

translates to an appropriate XML element in their corresponding SOAP/XML

representations which are exchanged with the client applications. This increases the

size of the SOAP/XML messages exchanged over the wire and also affects the run-

time performance depending on the size of the message. For example, this message is

an element centric XML representation of a DDL definition.

In NonStop SOAP 3.0 you have an option to treat a NON-OCCURS DDL leaf field as

an XML attribute for "document" style messages. This helps reduce the size of

SOAP/XML messages, as the DDL field name only occurs once.

Example 4-18. Element Centric XML Message

</MemberName>

</AccountDetails>

Note. Since the XML attribute is supported only for “document” style messages, there is no

multireference support for this feature.