You specify the localName element to customize the mapping of the local names of the request wrapper element. If the element value is specified in the localName element, you can also customize the type name of the wrapper element.

The precautions for specifying the localName element are as follows:

• Specify the localName element using one-byte alphanumeric characters and underscore (_). If other characters are specified, the operations might not function properly (error message is not output).
• Specify the same name for the localName element and the operation name. If the names vary, an error message is output to the standard error output and logs (KDJW61047-E). However, if the javax.xml.ws.RequestWrapper annotation does not exist, or if you specify a blank character ("") in the localName element of the javax.xml.ws.RequestWrapper annotation, a comparison is not done to check whether the names are the same and hence a message is not output.

You specify the targetNamespace element to customize the mapping of the name spaces of the request wrapper element.

In the targetNamespace element, the http:// or urn: protocol is specified as a name space. The following name space formats and strings can be specified:

• Protocol
  Code the name space protocol using the http:// or urn: protocol. If a protocol other than http:// or urn: (such as https://, file://) is coded, an error message is output to the standard error output and log (KDJW61042-E).
  Also, if you code the name space using the relative path, an error message is output to the standard error output and logs (KDJW61043-E).
  
• Name space coding format
  The following formats cannot be coded in the name space. If the following formats are used for coding, an error message is output to the standard error output and logs (KDJW61044-E):
  
  • 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
• Strings that can be coded
  In the segments separated using the separation characters, forward slash (/) or period (.), 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 the xsd:NCName type of the XML Schema specification.
  

  Table 16-22 Conditions for the strings that can be coded in the name space (javax.xml.ws.RequestWrapper)

  No.	Condition	Example of invalid string	Operation when an invalid string is specified
  1	Strings using only one-byte alphanumeric characters (0 to 9, A to Z, a to z)	http://Hitachi.com http://133.145.224.19/ http://[1080:2C14;D30:BA04:275:806:270C:418A]/	The operations might not function properly (error message is not displayed).
  2	Strings other than Java reserved words	http://hitachi.com/abstract	The operations might not function properly.
  3	Strings that do not begin with numeric characters	http://1hitachi.com

The className element specifies the class name of the generated request bean using a fully qualified name.

The precautions for specifying the className element are as follows:

• Specify the className element using one-byte alphanumeric characters, underscore (_), and dollar mark ($). If other characters are specified, the operations might not function properly (error message is not output).
• Specify a value complying with the Java identifier naming rules provided in the Java language specifications. If the value does not comply with the Java identifier naming rules, an error message is output to the standard error output and logs (KDJW61040-E).

Specify the partName element when customizing the mapping of the part name of the input message that references the request wrapper element.

Specify the partName with one-byte alphanumeric characters and underscore (_). The operation is not guaranteed if any other character is specified (no error message is output).