The following sections provide information about supported data types (both built-in and user-defined) and data binding:
As in previous releases, WebLogic Web Services support a full set of built-in XML Schema, Java, and SOAP types, as specified by the
JAX-RPC 1.1 specification, that you can use in your Web Service operations without performing any additional programming steps. Built-in data types are those such as integer
, string
, and time
.
Additionally, you can use a variety of user-defined XML and Java data types, including Apache XmlBeans (in package org.apache.xmlbeans
), as input parameters and return values of your Web Service. User-defined data types are those that you create from XML Schema or Java building blocks, such as <xsd:complexType>
or JavaBeans. The WebLogic Web Services Ant tasks, such as jwsc
and clientgen
, automatically generate the data binding artifacts needed to convert the user-defined data types between their XML and Java representations. The XML representation is used in the SOAP request and response messages, and the Java representation is used in the JWS that implements the Web Service. The conversion of data between its XML and Java representations is called data binding.
WARNING: | As of WebLogic Server 9.1, using XMLBeans 1.X data types (in other words, extensions of com.bea.xml.XmlObject ) as parameters or return types of a WebLogic Web Service is deprecated. New applications should use XMLBeans 2.x data types. |
The following sections describe the built-in data types supported by WebLogic Web Services and the mapping between their XML and Java representations. As long as the data types of the parameters and return values of the back-end components that implement your Web Service are in the set of built-in data types, WebLogic Server automatically converts the data between XML and Java.
If, however, you use user-defined data types, then you must create the data binding artifacts that convert the data between XML and Java.WebLogic Server includes the jwsc
and wsdl2c
Ant tasks that can automatically generate the data binding artifacts for most user-defined data types. See Supported User-Defined Data Types for a list of supported XML and Java data types.
The following table lists the supported XML Schema data types (target namespace http://www.w3.org/2001/XMLSchema
) and their corresponding Java data types.
For a list of the supported user-defined XML data types, see Java-to-XML Mapping for Built-In Data Types.
For a list of the supported user-defined Java data types, see Supported Java User-Defined Data Types.
The tables in the following sections list the user-defined XML and Java data types for which the jwsc
and wsdlc
Ant tasks can automatically generate data binding artifacts, such as the corresponding Java or XML representation, the JAX-RPC type mapping file, and so on.
If your XML or Java data type is not listed in these tables, and it is not one of the built-in data types listed in Supported Built-In Data Types, then you must create the user-defined data type artifacts manually.
The following table lists the XML Schema data types supported by the jwsc
and wsdlc
Ant tasks and their equivalent Java data type or mapping mechanism.
For details and examples of the data types, see the JAX-RPC specification.
The following table lists the Java user-defined data types supported by the jwsc
and wsdlc
Ant tasks and their equivalent XML Schema data type.
|
|||
|
See
Apache XMLBeans.
|
||
Note: | The following user-defined Java data type, used as a parameter or return value of a WebLogic Web Service in Version 8.1, is no longer supported: |
Note: | Additionally, generics are not supported when used as a parameter or return value. For example, the following Java method cannot be exposed as a public operation: |
Note: | public ArrayList<String> echoGeneric(ArrayList<String> in) { |