10 Using EJB 3.0 MDB API

This chapter describes the various options that you must configure in order to use an EJB 3.0 message-driven bean.

Note:

In this release, OC4J supports a subset of the functionality specified in the EJB 3.0 public review draft. You may need to make code changes to your EJB 3.0 OC4J application after the EJB 3.0 specification is finalized and OC4J is updated to full EJB 3.0 compliance. For more information, see "Understanding EJB Support in OC4J".

There are no OC4J-proprietary EJB 3.0 annotations. For all OC4J-specific configuration, you must still use the EJB 2.1 orion-ejb-jar.xml file.

Table 10-1 lists these options and indicates which are basic (applicable to most applications) and which are advanced (applicable to more specialized applications).

For more information, see:

Table 10-1 Configurable Options for an EJB 3.0 Message-Driven Bean

Options	Type
"Configuring an EJB 3.0 MDB to Use a Non-J2CA Message Service Provider"	Basic
"Configuring an EJB 3.0 MDB to Use a J2CA Message Service Provider"	Basic
"Configuring an MDB for Fast Undeploy on Windows"	Advanced
"Configuring an MDB for Oracle RAC Failover"	Advanced
"Configuring Bean Instance Pool Size"	Basic
"Configuring a Transaction Timeout for a Message-Driven Bean"	Advanced
"Configuring Listener Threads"	Advanced
"Configuring Maximum Delivery Count"	Advanced
Configuring Dequeue Retry Count and Interval	Advanced
"Configuring an Interceptor on an EJB 3.0 MDB Message Listener Method"	Advanced
"Configuring a Lifecycle Callback Method for an EJB 3.0 MDB"	Basic