Web Services - Java Data Mining: Strategy, Standard, and Practice - page 281

differentiate JDM Schema elements from the Web services-specific
elements. One of the reasons for splitting JDM Schema elements from
JDMWS is that JDM Schema elements can be used outside Web ser-
vices. (Note that these namespace URLs host neither JDM Schema
nor WSDL files. To get JDM Schema and WSDL files, download the
specification bundle from [JDM11 2006].)
The types element (line 8) declares the JDM Web services-specific
complex types and elements, xsd:import (line 12) is used to import the
JDM Schema types and elements that are used to define Web services-
specific types and elements. JDM WSDL follows the naming pattern
of using operation name for the associated complex types, elements,
and message names. For example, the saveObject operation's input
and outputs are represented using saveObjectElement (line 28) and
saveObjectResponseElement (line 29); these elements are of types
saveObject (line 14) and s aveObjectResponse (line 22), and the associ-
ated message names are IDataMining_saveObject (line 34) and
IDataMining_saveObjectResponse message (line 44). Because these
operation-related elements are defined at different parts of the WSDL
document, the use of the operation name simplifies their identifica-
tion in the WSDL document. For all messages the IDataMining _
prefix is used, so that when the JDMWS messages are mixed with
other Web services, the prefix identifies that the message is related to
data mining. These naming conventions are introduced to ease read-
ing of the WSDL documents and to get proper names for the
interfaces created from the WSDL by the code generators, such as
WSDL-to-Java, WSDL-to-C#. These mappings in the JAX-RPC
context are discussed further in Section 11.4.
The portType element defines the list of operations provided by
the Web service and defines the input, output, and fault messages
associated with the operations. For example, the saveObject operation
(line 42) element has sub-elements input (line 43), output (line 44), and
fault (line 45) used to define operation inputs, outputs, and exception
messages.
The binding element defines the protocol bindings for the message
format and transport protocol. JDMWS follows the WS-I Basic Profile
1.0 guidelines and uses the SOAP binding (line 50) with document
style (line 51) with literal content (line 55) for all the operations. For
more details about the message formats and WS-I Basic Profile 1.0
refer to [Haefel 2003].