Note the following when you create a WSDL for a SOAP reception:

• Specify a valid value for the name space (targetNamespace) for all XML schemata under the wsdl:types element.
• Define the XML schema within the supported range of the XML schema described in the manual Application Server SOAP Application Development Guide.
• You cannot specify the wsdl:import element.
• If the style attribute is document, do not specify the namespace attribute for the soap:body element.
• If the style attribute is rpc, specify the namespace attribute for the soap:body element.
• You cannot specify the soap:header element.
• The value for the name attribute of the soap:fault element must be the same as the value for the name attribute of the parent wsdl:fault element. Do not specify the namespace attribute.

When defining a WSDL, you can use unreserved characters defined by RFC3986 as well as Japanese characters. The following shows the characters that can be used for defining a WSDL, and contains notes on using the characters.

(a) For "document/literal"

You can use one-byte alphanumeric characters (A to Z, a to z, 0 to 9), underscore (_), and the following characters:

• Two-byte hiragana and katakana characters
• Two-byte Greek and Russian characters
• Repetition symbols (, , )
• Chinese characters (included in the first and second standards of JIS X 0208)

For attributes where the data type of WSDL is anyURI, you can also use the following characters:

• Hyphens (-)
• Periods (.)
• Tildes (~)

(b) For "rpc/literal"

You can use one-byte alphanumeric characters (A to Z, a to z, 0 to 9), and underscore (_). For attributes where the data type of WSDL is anyURI, you can also use the following characters:

• Hyphens (-)
• Periods (.)
• Tildes (~)