The default interceptor is applicable to all the components included in EJB-JAR.

In a DD, you can specify the information of the default interceptor by coding the <interceptor-binding> tag below the <ejb-jar> tag.

The following table describes the components to be specified below the <interceptor-binding> tag:

Table 2-46 Components (default interceptor) to be specified below the <interceptor-binding> tag when using a DD

The value of the components specified in any other tag is not applied.

The following is an example of coding of the DD when the default interceptor is used:

  
<ejb-jar>
    ...
  <assembly-descriptor>
   <interceptor-binding>
     <description xml:lang="en">Default Interceptor</description>
     <ejb-name>*</ejb-name>
     <interceptor-class>test.ejb30.MyDefaultIC</interceptor-class>
     <interceptor-class>test.ejb30.MyDefaultIC2</interceptor-class>
   </interceptor-binding>
  </assembly-descriptor>
    ...
</ejb-jar>

In this example of coding, test.ejb30.MyDefaultIC and test.ejb30.MyDefaultIC2 are specified as the default interceptor classes.

• Rules for specifying the interceptor class

The specification method of the class name in the interceptor-class tag conforms to the EJB 3.0 specification. Specify as per the following rules:

• You can specify one interceptor class name in one interceptor-class tag.
• You can code multiple interceptor-class tags. If you code multiple interceptor-class tags, the interceptor is invoked in the order in which you have coded.
• You can specify the interceptor method in an interceptor class, specified in the interceptor-class tag, with the following annotations:
• @AroundInvoke
• @PostConstruct
• @PreDestroy

For details on annotations, see 2. Dependency Injection and Annotation corresponding to the annotation servers in the uCosminexus Application Server API Reference Guide.

The class level interceptor is applicable to the specified classes. This point describes how to set a class level interceptor by using a DD and by using the EJB-JAR property file in the execution environment.

In a DD, you can specify the information of the class level interceptor by describing the <interceptor-binding> tag below the <ejb-jar> tag.

The following table describes the elements below the <interceptor-binding> tag.

Table 2-47 Elements (class level interceptor) to be specified below the <interceptor-binding> tag when using a DD tag

Note that elements are not specified in the <method> tag.

The method level interceptor is applicable to the specified business methods. This point describes how to set a method level interceptor by using a DD and by using the EJB-JAR property file in the execution environment.

In a DD, you can specify the information of the method level interceptor by describing the <interceptor-binding> tag below the <ejb-jar> tag.

The following table describes the elements below the <interceptor-binding> tag.

Table 2-48 Elements (method level interceptor) to be specified below the <interceptor-binding> tag when using a DD tag

The following table describes the range of the business methods that define the method level interceptor when you specify a business method in the <method-name> tag and you omit the value specified for the <method-params> tag or you specify the argument list in the <method-params> tag. Note that when * (wild card) is specified in the <method-name> tag, the definition of the method level interceptor is not used.

Table 2-49 Range of business methods that define the method level interface

Applicable rules for method level interceptor

The definition of the method level interceptor that is used when executing a business method is determined in the following order:

1. If a definition completely matches with the business method to be executed, the method name specified in the <method-name> tag, and the argument list specified in the <method-params> tag, then the definition of that method level interceptor is used.
2. If the business method to be executed and the method specified in the <method-name> tag match and the argument list is not specified in the <method-params> tag of a definition, then the definition of that method level interceptor is used.
3. If a method level interceptor in which the business method to be executed and the method specified in the <method-name> tag are matching, is not defined, then the method level interceptor definition is not used.

Note that when the business method to be executed corresponds to both definitions, namely the definition in which the method specified in the <method-name> tag and the argument list specified in the <method-params> tag match completely, and the definition in which the method specified in the <method-name> tag is matching and the argument list is not specified in the <method-params> tag, then the definition that completely matches with the method name and argument list is used.

Also, the method level interceptor specified using annotations is handled as a definition in which the method names and the argument list match completely. If you want to overwrite the method level interceptor specified using annotations in DD, you must describe the interceptor in DD by using a definition in which the method names and the argument list match completely.