User`s guide

IBM Lotus Notes, Domino, Domino Designer 8 Release Notes

Domino Designer, Domino Server

Web Services and Arrays

By default, the WSDL representations generated by Domino Designer 8 for arrays in a LotusScript or

Java Web service implementation are of the following forms:

XML "literal" form for Web service design elements that have rpc/literal, document/literal, or wrapped

SOAP message formats:

<element name="elem" minOccurs="0" maxOccurs="unbounded"

type="[array element type]"/>

</sequence>

</complexType>

the SOAP-encoded ("SOAPENC") form for Web service design elements that have the rpc/encoded

SOAP message format:

<attribute ref="soapenc:arrayType" wsdl:arrayType="[array

element type]"/>

</restriction>

</complexContent>

</complexType>

In addition, the XML "literal" form is also generated from Java Web service implementations for what are

commonly known as Java Bean "indexed" properties in a Java Web service value type.

During WSDL importing, XML "literal" arrays are always supported, regardless of SOAP message format.

However, Domino Designer 8 no longer imports WSDL descriptions using SOAP-encoded ("SOAPENC")

arrays together with "literal" SOAP message formats (i.e. rpc/literal, document/literal, or wrapped).

The remainder of this Release Note is specific to LotusScript Web services .

Empty Arrays

Empty arrays in a SOAP request or response (i.e. literal array elements that are completely absent, or

elements with a SOAPENC "arrayType" attribute, but no array content children) are supported for Domino

8.0 Web services by passing uninitialized dynamic arrays to the Domino 8.0 provider or consumer.

This is a change in behavior from Domino 7.x Web service providers (which still either trigger runtime

SOAP faults, or receive arrays of length 1). This change suggests that the receiving consumer or

provider should be implemented to handle ErrUninitDynArray errors, for detecting that empty arrays have

been received during attempts to access them.

119