When developing Web Services starting from SEI, compile Web Services Implementation Class by using the javac command. However, when compiling Web Services Implementation Class by using the javac command, the following mapping errors are not checked:

• Default mapping
  For details, see 1.4.2(1)(a) Default mapping.
  
• Customization of mapping (annotation)
  For details, see 1.4.2(1)(b) Customization of mapping.
  

For this reason, if definitions unsupported in the JAX-WS functionality are included in Web Services Implementation Class, the process of starting Web Service or acquiring the metadata after Web Service starts successfully, might lead to errors. To avoid errors, you must execute the cjwsgen command in Web Services Implementation Classes compiled by using the javac command and check for the errors in advance. If Web Service fails to start, the following error messages are output to the log or the standard error output.

• KDJW00003-E
• KDJW00005-E
• KDJW00006-E
• KDJW00007-E
• KDJW00008-E
• KDJW20026-E
• KDJW20027-E
• KDJW20041-E
• KDJW20042-E
• KDJW40011-E
• KDJW40013-E

The JAX-WS engine dynamically generating a JavaBeans class is an on-memory processing. As compared to the process in which a JavaBeans class is statically generated, the starting performance of Web Service, therefore, declines when the JAX-WS engine puts a load on the Web Service when dynamically generating a JavaBeans class. However, the process of dynamically generating a JavaBeans class does not require the process of reading the WAR file, thereby reducing the load.

Because the JavaBeans class that is statically generated by JAX-WS is the same as the JavaBeans class that is statically generated by the cjwsgen command, the performance of the SOAP communication after you start Web Service is the same irrespective of whether the JavaBeans class is generated dynamically or statically.