This subsection describes the notes on using the DI.

• The notes on obtaining the Stateful Session Bean references when the DI is used are as follows:
  
  • When the configuration of the J2EE application is such that Stateful Session Bean is invoked from the servlet, obtain the Stateful Session Bean references via the JNDI instead of using the DI.
  • When the configuration of the J2EE application is such that Stateful Session Bean is invoked from Stateless Session Bean or Singleton Session Bean and when the business interface of Stateful Session Bean is injected in Stateless Session Bean by using the DI, the DI is executed every time the business method of Stateless Session Bean is invoked or every time the timeout method is invoked.
• If a resource type that cannot be specified with the @Resource annotation is specified, an exception occurs during import.
• The name attribute of the @EJB and @Resource annotations corresponds to the elements of the ejb-jar.xml tags described in the following table. Consequently, when you define the references for the Enterprise Beans and resources using annotations, specify the settings so that the name attribute of the @EJB and @Resource annotations is not duplicated with the elements specified in the ejb-jar.xml tags corresponding to the name attribute. The following table describes the ejb-jar.xml tags corresponding to the name attribute.
  

  Table 12-8 ejb-jar.xml tags corresponding to the name attribute

  Annotations and attributes	ejb-jar.xml tags corresponding to the name attribute
  @EJB name()	<ejb-ref-name> tag under the <ejb-ref> tag
  	<ejb-ref-name> tag under the <ejb-local-ref> tag
  @Resource name()	<env-entry-name> tag under the <env-entry> tag
  	<res-ref-name> tag under the <resource-ref> tag
  	<resource-env-ref-name> tag under the <resource-env-ref> tag

• Exceptions might occur when a Web application that uses DI is reloaded. The cases in which exceptions occur are as follows:
  
  • When the loading of the class that defines the DI target (the target in which the reference is injected by using the DI functionality) or the reference destination class fails
  • When the fields and methods corresponding to the DI target name are deleted after reloading and no longer exist
  If an exception occurs, the KDJE53904-W message is output to the message log and the processing continues. Although the processing continues, you cannot execute the DI and requests for the target instances. As a result, when this message is output, modify the Web application and re-execute the reload operation.