User`s guide
IBM Lotus Notes, Domino, Domino Designer 8 Release Notes
Fixed-Size and Dynamic Arrays
Fixed arrays are supported only when they are used within a Type declaration. For example:
Type MyType
myArray(2,2) As Long ' fixed-size array
End Type
Dynamic arrays are supported only when used within a Class declaration: For example:
Class MyClass
myArray() As Long ' dynamic array
End Class
Using arrays in other constructs may cause unpredictable results, including causing server stability
problems (see SPR# TCAR6HPUH6).
Multidimensional Arrays
Serialization of multidimensional SOAP-encoded arrays are not currently supported. Such a serialization
results in a single-dimension SOAP array containing all of the LotusScript array's elements, but with an
incorrect array-size value in the "arrayType" attribute. (see SPR# TCAR6HPT4L)
Support for deserialization of multidimensional SOAP-encoded arrays was added with the 7.0.1 release.
There are, however, some limitations:
z
Multidimensional arrays are not supported when the array is a member of a LotusScript "Type"
statement, or when the elements in the array are defined with a LotusScript "Type" statement.
For such cases, it is suggested that a "Class" construct be used instead.
z
So-called "
j
a
gg
ed" arrays are not supported. An multi-dimensional array is considered to be
"
j
a
gg
ed" when sub-arrays within a given dimension are of varying lengths. For example:
<a xsi:type="soapenc:Array" soapenc:arrayType="xsd:int[][2]"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item soapenc:arrayType="xsd:int[1]">
<item>100</item>
</item>
<item soapenc:arrayType="xsd:int[2]">
<item>200</item>
<item>300</item>
</item>
</a>
z
The optional "asize" component of the SOAP "arrayType" syntax is not recognized. The length of
deserialized arrays will be based solely on the actual number of array elements present in the
SOAP message. For example, for an array with the arrayType attribute of "xsd:string[10]", but
with 5 or 15 actual items, the length of the array would be 5 or 15 respectively, not 10.
z
The SOAP attributes "position" and "offset", for sparse and partially transmitted arrays, are not
supported.
Domino Designer
XML schema mechanisms "include" and "import" are not supported
The XML schema mechanisms "include" and "import" are not supported. That is, any XML schema
defined in an imported WSDL document must not refer to any external XML schema documents.
120