The Java wrapper exception class and the fault are mapped in accordance with the JAX-WS 2.2 specifications. The following figure shows an example of mapping:

Figure 16-8 Example of mapping the exception class to the fault

The following are the rules for mapping the wrapper exception class to the fault:

• If the wrapper exception class has the javax.xml.ws.WebFault annotation and the getFaultInfo method that returns the fault bean, the fault bean is not generated when you execute the command as the fault bean already exists.
• If the wrapper exception class does not have the javax.xml.ws.WebFault annotation and the getFaultInfo method, a fault bean is generated with a name in which "Bean" is added as a suffix to the wrapper exception class name.
• The generated fault bean has the same type or name properties that the wrapper exception class and its parent class have and the type or name properties similar to all the getter except the getter named getCause, getLocalizedMessage, and getStackTrace inherited from Throwable and the getter named getClass inherited from java.lang.Object.
• The javax.xml.bind.annotation.XmlType annotation is annotated in the generated fault bean.
  In the annotated javax.xml.bind.annotation.XmlType annotation, an exception class name is set in the name element, an SEI name space is set in the namespace element, and all the property names that the wrapper exception class has are set in the propOrder element. The property name of the propOrder element is set with the String type array sorted in an ascending order according to the Unicode value of each character.
  For details on the javax.xml.bind.annotation.XmlType annotation, see 16.2.12 javax.xml.bind.annotation.XmlType annotation.
  
• The fault message name is mapped with the same name as the wrapper exception class name. Also, the fault message part name is mapped with the fixed value fault.
• You can define up to 255 exceptions to be thrown in one method. If 256 or more exceptions are defined, a warning message is output to the standard error output and log and the processing continues (KDJW61027-W).
• If the exception class thrown by the method is not found, a compilation error occurs.

The following are the conditions for the wrapper exception class:

• The wrapper exception class might inherit the exception classes of java.lang.Exception, java.lang.RuntimeException, and java.rmi.RemoteException. However, the java.lang.RuntimeException and java.rmi.RemoteException, and its sub-classes are not handled as the wrapper exception class.
• The same wrapper exception class might be thrown by multiple methods in the same SEI.

In the wrapper exception class name, you can code strings that fulfill all the conditions described in the following table. The wrapper exception class name is used in WSDL even though an annotation is specified, so the name must comply with the conditions described in the following table:

Table 16-8 Conditions for strings that can be coded in the wrapper exception class name

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) and underscore (_)	Hitachi_exception	The operations might not function properly (error message is not displayed).
2	Strings complying with the naming rules of the Java identifiers provided in the Java language specifications	Abstract	When the apt command is executed, a compilation error occurs and the processing ends. For details, see the JDK documentation.

The fault bean name must be unique in the package. However, the uppercase or lowercase differences are ignored. If a name conflict occurs between the fault bean and the JavaBean generated concurrently in the package, an error message is output to the standard error output and logs (KDJW61065-E).

If the name is duplicated with an existing class, the name is overwritten. However, if that class is included in the argument of the apt command, the error is checked with the apt command.

The global element (local name and name space) mapped from the fault bean must be unique in WSDL. If the global element is not unique, the operations might not function properly.