Web Service Mobile Business Object Limitations

This section describes known limitations when binding an MBO to Web service data sources.

Unsupported types

These Web service types are currently unsupported:

• Recursive definitions of element types.
• Soapenc encoded arrays.
• gDay, gYear, gMonth, gYearMonth
• HexBinary datatypes are not supported, instead use base64Binary.
• Unsupported datatypes are either ignored or recognized as a String.

Unsupported derived or complex types

These complex datatype scenarios are currently unsupported for Web service MBOs:

• This structure is not supported:

  Structure A[]: 
  x of type struct B[]. 
  (y of type struct C[]) 
  

  but does support:

  Struct A[]: 
  < scalar type > x, 
  y of type Struct B[] 
  

Unsupported schema constructs

• Schema used as element data (i.e. an element is a schema).

Unsupported Web service operations

• One way operation

MBO Mapping restrictions

• For WSDL and SOAP Web service data sources , if an Update operation that uses the Immediately update the cache operation cache policy does not have an XSLT, an error message displays:

  The ''UPDATE'' operation 'Customer- > updateStudent()' 
  with ''Immediately update the cache'' cache policy does not 
  have XSLT. 

• If namespaces are used, the XSL namespace must be defined in the WSDL to parse the namespaced SOAP response message nodes.