Web service data types

The following table lists Java data types and shows the corresponding web service data type.

Java data type

Web service data type

java.lang.byte[]

xsd:base64Binary

java.lang.Boolean

xsd:boolean

java.util.Date

The DATE type, which is defined in a service WSDL as follows:

<complexType name="DATE">

<sequence>

<element maxOccurs="1" minOccurs="0" name="date" type="xsd:dateTime" />

<element maxOccurs="1" minOccurs="0" name="calendar" type="xsd:dateTime" />

</sequence>

</complexType>

If a LiveCycle service operation takes a java.util.Date value as input, the SOAP client application must pass the date in the DATE.date field. Setting the DATE.calendar field in this case causes a runtime exception. If the service returns a java.util.Date, the date is retuned in the DATE.date field.

java.util.Calendar

The DATE type, which is defined in a service WSDL as follows:

<complexType name="DATE">

<sequence>

<element maxOccurs="1" minOccurs="0" name="date" type="xsd:dateTime" />

<element maxOccurs="1" minOccurs="0" name="calendar" type="xsd:dateTime" />

</sequence>

</complexType>

If a LiveCycle service operation takes a java.util.Calendar value as input, the SOAP client application must pass the date in the DATE.caledendar field. Setting the DATE.date field in this case causes a run-time exception. If the service returns a java.util.Calendar, then the date is returned in the DATE.calendar field.

java.math.BigDecimal

xsd:decimal

com.adobe.idp.Document

BLOB

java.lang.Double

xsd:double

java.lang.Float

xsd:float

java.lang.Integer

xsd:int

java.util.List

MyArrayOf_xsd_anyType

java.lang.Long

xsd:long

java.util.Map

The apachesoap:Map, which is defined in a service WSDL as follows:

<schema elementFormDefault="qualified" targetNamespace="http://xml.apache.org/xml-soap" xmlns="http://www.w3.org/2001/XMLSchema">

<complexType name="mapItem">

<sequence>

<element name="key" nillable="true" type="xsd:anyType"/>

<element name="value" nillable="true" type="xsd:anyType"/>

</sequence>

</complexType>

<complexType name="Map">

<sequence>

<element maxOccurs="unbounded" minOccurs="0" name="item" type="apachesoap:mapItem"/>

</sequence>

</complexType>

</schema>

The Map is represented as a sequence of key/value pairs.

java.lang.Object

xsd:anyType

java.lang.Short

xsd:short

java.lang.String

xsd:string

org.w3c.dom.Document

The XML type, which is defined in a service WSDL as follows:

<complexType name="XML">

<sequence>

<element maxOccurs="1" minOccurs="0" name="document" type="xsd:string" />

<element maxOccurs="1" minOccurs="0" name="element" type="xsd:string" />

</sequence>

</complexType>

If a LiveCycle service operation accepts an org.w3c.dom.Document value, pass the XML data in the XML.document field.

Setting the XML.element field causes a runtime exception. If the service returns an org.w3c.dom.Document, then the XML data is returned in the XML.document field.

org.w3c.dom.Element

The XML type, which is defined in a service WSDL as follows:

<complexType name="XML">

<sequence>

<element maxOccurs="1" minOccurs="0" name="document" type="xsd:string" />

<element maxOccurs="1" minOccurs="0" name="element" type="xsd:string" />

</sequence>

</complexType>

If a LiveCycle service operation takes an org.w3c.dom.Element as input, pass the XML data in the XML.element field.

Setting the XML.document field causes a runtime exception. If the service returns an org.w3c.dom.Element, then the XML data is retuned in the XML.element field.

Adobe Developer website

The Adobe Developer website contains the following article that discusses invoking LiveCycle services using the web service API:

Creating form rendering ASP.NET applications

Invoking web services using custom components

Note: Invoking web services using custom components describes how to create a LiveCycle component that invokes third party web services.

// Ethnio survey code removed