The name of the method of SEI and the WSDL operation are mapped in accordance with the JAX-WS 2.2 specifications. The following figure shows an example of mapping:

Figure 16-3 Example of mapping the name of method of SEI to an operation

The following conditions must be fulfilled to make the SEI method public:

• The access modifier is public
• A static modifier or final modifier has not been applied
• If annotated by the javax.jws.WebMethod annotation, the exclude element of the javax.jws.WebMethod annotation is not true

The following are the rules for mapping the name of method of SEI to the operation:

• Regardless of whether the javax.jws.WebMethod annotation is present, all the public methods of SEI are mapped to the WSDL operation.
• If the endpointInterface element of the javax.jws.WebService annotation is not used, it is considered that an implicit SEI has the public method of the Web Service Implementation Class and is mapped to the WSDL operations. For details about the methods mapped to the implicit SEI, see 16.2.6 javax.jws.WebMethod annotation.
• When a Web Service Implementation Class inherits another Web Service Implementation Class, all the methods meeting the following conditions are mapped to WSDL operations:
  (Conditions)
  The public method in the Web Service Implementation Class and parent Web Service Implementation Class, wherein the exclude element of the javax.jws.WebMethod annotation is not true.
  
• If a Web Service Implementation Class inherits another Web Service Implementation Class and overrides the parent class methods, the public methods overridden in the Web Service Implementation Class are mapped to the WSDL operations. The methods overridden in the parent class are not mapped.
• In the public methods that can be defined in SEI and the public methods of Web Service Implementation Class, you can define 255 public methods. If 256 or more public methods are defined, a warning message is output to the standard error output and log and the processing continues (KDJW61026-W).
• The value of the name attribute of the wsdl:operation element mapped from the name of method of SEI must be unique in WSDL. If a name conflict occurs, an error message is output to the standard error output and log (KDJW61060-E).
• If no public method exists, the system outputs an error message to the standard error output and log, and ends the operation (KDJW61093-E).

In the method name, you can code strings that fulfill all the conditions described in the following table:

Table 16-4 Conditions for strings that can be coded in the method 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_sei	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.

However, when all the following annotations are used, you can code strings complying with the naming rules of the Java identifiers provided in the Java language specifications:

• The operationName element of the javax.jws.WebMethod annotation
• The localName element and className element of the javax.xml.ws.RequestWrapper annotation (for wrapper style)
• The localName element and className element of the javax.xml.ws.ResponseWrapper annotation (for wrapper style)
• The name element of the javax.jws.WebParam annotation (for non-wrapper style)
• The name element of the javax.jws.WebResult annotation (for non-wrapper style)

When using the method overloading, a name conflict occurs in the default mapping; therefore, you must customize the name using annotation so that the name is unique.

The following table describes the locations where the name conflict occurs due to overloading and their references:

Table 16-5 Location where the name conflict occurs due to overloading and references

No.	Location where the name conflict occur	Annotation reference
		Wrapper style	Non-wrapper style
1	Operation name	16.2.6(2)
2	Global element of input#	16.2.16(1), 16.2.16(2)	16.2.7(2), 16.2.7(5)
3	Global element of output#	16.2.17(1), 16.2.17(2)	16.2.8(2), 16.2.8(4)
4	Request bean class name	16.2.16(3)
5	Response bean class name	16.2.17(3)

#

If you customize either the local name or name space, the name conflict will not occur.