With the Cosminexus JAX-WS functionality, as long as you do not violate the limitations for the xsd:NCName type in the XML Schema specifications, you can use one-byte alphanumeric characters (0 to 9, A to Z, a to z) and underscore (_). If you use characters other than one-byte alphanumeric characters and underscore, the operations are not guaranteed.

This point describes the coding of the SOAP Body and SOAP Header that are coded as the child elements of the wsdl:input element and wsdl:output element, and the coding of the wsdl:part element referenced from the SOAP Body and SOAP Header.

The description hereafter uses the SOAP 1.1 specifications for the examples. For the SOAP 1.2 specifications, substitute and read the Namespace and the element names, and the attribute values.

(a) When the SOAP Header is not defined

Whether you code the parts attribute in the soap:body element or not, code only one wsdl:part element in the child element of the wsdl:message element referenced from the wsdl:input element or wsdl:output element that are the parent elements.

The following figure shows an example of coding when the soap:header element is not coded.

Figure 20-3 Example of coding when the soap:header element is not coded

(b) When the SOAP Header is defined

To code the soap:header element, define the coding according to the following contents:

• In the message attribute of the soap:header element, specify the wsdl:message element referenced from the wsdl:input element or wsdl:output element that are the parent elements.
• In the part attribute of the soap:header element, specify the wsdl:part element declared beneath the wsdl:message element specified in the message attribute. If an undeclared wsdl:part element is specified, an error message (KDJW51022-E) is output to the standard error output and the log, and the processing of the cjwsimport command ends (KDJW51022-E).
• The parts attribute of the soap:body element cannot be omitted. Specify which of the multiple wsdl:part child elements of the wsdl:message element referenced from the wsdl:input element or wsdl:output element, which are the parent elements, will be bound to the soap:body element. If you do not want to bind the elements, specify an empty string.
  If the wsdl:part element of the wsdl:message elements that are not referenced or a non-existent wsdl:part element is specified in the parts attribute of the soap:body element, an error message (KDJW51021-E) is output to the standard error output and the log, and the processing of the cjwsimport command ends. Also, if the parts attribute of the soap:body element is not specified, an error message (KDJW51179-E) is output to the standard error output and the log, and the processing of the cjwsimport command ends.
  

The following figure shows an example of coding when the soap:header element is coded.

Figure 20-4 Example of coding when the soap:header element is coded

You can specify a URL with the following format in the location attribute of the soap:address element or the soap12:address element:

• Protocol^#1://host-name^#2/path-part^#3
  (Example) http://hitachi.com/jaxws/service/UserInfoPort
  
• Protocol ^#1://host-name ^#2:port-number^#4/path-part^#3
  (Example) http://hitachi.com:80/jaxws/service/UserInfoPort
  

#1

You can only specify http:// or https:// as the Namespace. You cannot specify other protocols. If you specify a protocol other than http:// and https:// is specified, the operations are not guaranteed.

#2

You can specify a string complying with the RFC2396 specifications. You can specify the string in the IPv4 and IPv6 format.

However, you cannot specify the following formats. If the following formats are specified, the operations are not guaranteed:

• Query string (Example) http://example.com/?a=b
• Anchor (Example) http://example.com/index.html#anchor
• Port number (Example) http://example.com:8080/
• User name/ Password (Example) http://user:password@example.com
• Percent-encoded characters (Example) http://%E4%BD%BF%E7%94%A8

#3

You can specify a string using only the numeric characters 0 to 9. If other characters are specified, the operations are not guaranteed.

#4

You can specify a string complying with the RFC2396 specifications. You can also specify percent-encoded characters ((Example) http://%E4%BD%BF%E7%94%A8).