• For mapping from a WSDL of request-response operations
  The wrapper child element to be referenced from the message part of a WSDL (define one wsdl:input element and one wsdl:output element , and zero or more wsdl:fault elements) of the request-response operations and the return values and parameters of the Java method are mapped. The following figure shows the example of mapping.
  

  Figure 15-4 Example of mapping message parts to parameters and return values (request-response operation)

  

• For mapping from a WSDL of one-way operations
  The wrapper child element to be referenced from the message part of a WSDL (define only one wsdl:input element) of the one-way operation and the parameters of the Java method are mapped. The following figure shows an example of mapping.
  

  Figure 15-5 Example of mapping of message parts and parameters (one-way operations)

  

During mapping, the first letter of the wrapper child elements names of the WSDL is converted to lower-case letter in both, the request-response operations and one-way operations.

Before conversion: WrapperName

After conversion: wrapperName

• Relationship between part types and mapping to Java source
  The following table describes the relationship between the part types (in, inout, out) and the mapping to Java source:
  

  Table 15-8 Mapping of part types to Java sources (Wrapper style)

  No.	WSDL part types	Mapping to Java
  		Mapped to	Mapping method
  1	in	Parameter	Not mapped using javax.xml.ws.Holder<T> class. Mapped using classes such as java.lang.String.
  2	inout	Parameter	Mapped using javax.xml.ws.Holder<T> class. #
  3	out	Parameter	Mapped using javax.xml.ws.Holder<T> class. #
  4		Return value	Not mapped using javax.xml.ws.Holder<T> class. Mapped using classes such as java.lang.String.

  #

  If the wrapper child element type is a type that is mapped with JAXB specifications to a Java primitive type such as xsd:int, since the type corresponds to primitive, set up a non-null value for the Holder instance for sending.

  
  

In the wrapper child element name, you can code a string that fulfills all the conditions described in the following table. However, when customizing with the binding declaration, you can code the strings that can be used as xsd:NCName type of the XML Schema specification.

Table 15-9 Conditions for strings that can be coded in the wrapper child element name (wrapper style)

#

You cannot code strings such as Abstract where the first character of the Java reserved word is in upper case (since the first character is converted into a lower case character due to mapping).

When the wrapper child element that appears in the input message or output message is coded several times in WSDL, handling of the wrapper child elements differs depending on whether the local name and the XML Schema type of wrapper child elements are same or different, as described in the following table:

Table 15-10 Different handling of wrapper child elements depending on local name and XML Schema type of wrapper child elements

When you define same wrapper child elements and different wrapper child elements multiple times in a WSDL file as the composite-type child elements, and execute the cjwsimport command by specifying this WSDL file, SEI will be mapped with the non-wrapper style.

The following is an example of the WSDL file where SEI is mapped with the non-wrapper style:

<wsdl:definitions name="TestJaxWsService"
                  xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/
                  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                  xmlns:tns="http://example.com/example"
                  targetNamespace="http://example.com/example">
 
   <xsd:element name="getUserData" type="tns:getUserData"/>
    ...
   <xsd:complexType name="getUserData">
     <xsd:sequence>
       <xsd:element name="in0"  type="xsd:string"/>
       <xsd:element name="in0"  type="xsd:string"/>
       <xsd:element name="hoge" type="xsd:string"/>
     </xsd:sequence>
   </xsd:complexType>
   ...
  </xsd:schema>
 </wsdl:types>
...
 <wsdl:message name="getUserDataRequest">
  <wsdl:part name="inputParameters" element="tns:getUserData"/>
 </wsdl:message>
 ...
</wsdl:definitions>
 

• When you map the wrapper child element to Java, even if the parameter types of the method are different, if the parameter names are the same, an error message is output in the standard error output and log and the processing ends.
• The parameters mapped from the wrapper child elements of in and inout are mapped in the order of appearance of the corresponding wrapper child elements in the wrapper element. The parameters mapped from the wrapper child element of out are mapped in the order of appearance of the corresponding wrapper child elements in the wrapper element.
• If the wrapper child elements of in, inout, and out are mixed, the wrapper child elements of in and inout are mapped in the order of appearance of the corresponding wrapper child elements in the wrapper element. Then the wrapper child element of out is mapped in the order of appearance of the corresponding wrapper child elements in the wrapper element.
• The parameters of out (excluding the parameters mapped to the return value) and inout that are Java primitive type, Java array type, and user-defined type are mapped to the Holder type (javax.xml.ws.Holder<T>) in the Java source. The example is as follows:
  

  Example:

  Data type of the part of out and inout: java.lang.String

  Data type after mapping to Java: javax.xml.ws.Holder<java.lang.String>

• Specify 0 to 254 as the number of parameters after mapping to Java. If you specify 255 or more parameters, an error message is output in the standard error output and log and the processing ends (KDJW51016-E).

If there is 1 wrapper child element of out or if the local name of the wrapper child element of out is "return", that value is mapped to the return value of the method. However, even if the types are different, if you code multiple wrapper child elements with the local name "return", an error message is output in the standard error output and log and the processing ends.