11 Deployment Elements and Annotations for MDBs
Each row in Table 11-1 describes a deployment element (used in an EJB deployment descriptor) and its associated configuration property (specified in annotations). Not all elements have associated properties.
For information about using deployment descriptors versus using annotations in MDBs, see Programming EJB 3.2 Compliant MDBs.
Note:
For those elements that have an associated configuration property, Oracle recommends that you use that property instead of the element.Table 11-1 is organized as follows:
-
Each element in the Element column is followed in parentheses by the name of the deployment descriptor in which the element is used. Elements in the
weblogic-ejb-jar.xmldescriptor link to a more complete explanation of the element in weblogic-ejb-jar.xml Deployment Descriptor Reference in Developing Enterprise JavaBeans, Version 3.2, for Oracle WebLogic Server. For elements inejb-jar.xml, see the schema athttp://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/ejb-jar_3_2.xsd. -
Unless otherwise noted, all the properties listed in the Configuration Property column are activation configuration properties, that is, properties defined using
@ActivationConfigPropertyannotations or using anactivation-config-propertyelement in themessage-drivenstanza of anejb-jar.xmldescriptor. For more information about using@ActivationConfigProperty, see Programming EJB 3.2 Compliant MDBs.Note:
Based on the Enterprise JavaBean specification, the
javax.ejb.ActivationConfigPropertyannotation is used for MDBs only. This annotation is not used for session or entity beans. -
The Configuration Property column also lists annotations and properties that are not
@ActivationConfigPropertyproperties. In those cases, the property is followed by the name of the annotation and by theimportstatement required for using that annotation.
Table 11-1 Deployment Elements and Annotations for MDBs
| Element | Configuration Property | Description | Allowable Values | Default |
|---|---|---|---|---|
|
( |
|
Notifies the JMS provider that the message was received and processed. The acknowledgement mode is ignored if using container-managed transactions. (The acknowledgement is performed in the context of the transaction.) |
|
|
|
( |
|
The lookup name of a JMS connection factory that will be used to connect to the JMS provider from which a JMS message-driven bean is to receive messages. |
Valid lookup name |
|
|
( |
|
The JNDI name of the JMS ConnectionFactory that the MDB looks up to create its queues and topics. See How to Set connection-factory-jndi-name. |
Valid JNDI name |
|
|
( |
|
Maps to a resource within a JMS module defined in |
Valid resource within a JMS module |
n/a |
|
( |
|
The lookup name of a JMS queue or topic from which a JMS message-driven bean is to receive messages. |
Valid lookup name |
n/a |
|
( |
|
The JNDI name used to associate an MDB with an actual JMS queue or topic deployed in the Oracle WebLogic Server JNDI tree. See How to Set destination-jndi-name. |
Valid JNDI name |
n/a |
|
( |
|
Maps to a resource within a JMS module defined in |
Valid resource within a JMS module |
n/a |
|
( |
n/a |
This optional element allows you to specify a particular WorkManager for the bean. See Tuning Message-Driven Beans in Tuning Performance of Oracle WebLogic Server. |
Valid execute queue name |
n/a |
|
( |
|
Specifies whether an MDB that accesses a WebLogic JMS distributed destination (topic or queue) in the same cluster consumes from all distributed destination members or only those members local to the current Oracle WebLogic Server instance. May not apply to all use cases. See JMS Distributed Destinations, and Configuring and Deploying MDBs Using JMS Topics. |
|
|
|
( |
|
Indicates whether you want durable topic subscriptions to be automatically deleted when an MDB is undeployed or removed. |
|
|
|
( |
See the |
Indicates whether or not you want the EJB container to generate a unique |
|
|
|
( |
n/a |
Sets the initial size of the free pool. Oracle WebLogic Server populates the free pool with the specified number of bean instances for every bean class at startup. Populating the free pool in this way improves initial response time for the MDB, because initial requests for the bean can be satisfied without generating a new instance. |
|
0 |
|
( |
|
The initial context factory that the EJB container uses to create its connection factories. See How to Set initial-context-factory. |
Valid name of an initial context factory |
|
|
( |
|
The initial number of seconds to suspend an MDB's JMS connection when the EJB container detects a JMS resource outage. See Configuring Suspension of Message Delivery During JMS Resource Outages. |
Any integer |
|
|
( |
|
The client identifier that will be used when connecting to the JMS provider from which a JMS message-driven bean is to receive messages. |
n/a |
Depends on the |
|
( |
|
The client ID for the MDB when it connects to a JMS destination. Optional. Used for durable subscriptions to JMS topics. For more information, see Topic Subscription Identifiers. |
n/a |
Depends on the |
|
( |
|
The number of seconds between attempts by the EJB container to reconnect to a JMS destination that has become unavailable. See Migration and Recovery for Clustered MDBs. |
Any integer |
|
|
( |
n/a |
The maximum number of bean instances in an MDB free pool. The actual number of instances is also limited by thread pool size as well as other factors. See Tuning Message-Driven Beans in Tuning Performance of Oracle WebLogic Server. |
|
1000 |
|
( |
|
Specifies the maximum number of messages that can be in a transaction for this MDB. |
All positive integers |
n/a |
|
( |
|
The maximum number of seconds to suspend an MDB's JMS connection when the EJB container detects a JMS resource outage. See Configuring Suspension of Message Delivery During JMS Resource Outages. |
Any integer |
|
|
( |
|
Specifies the type of the JMS destination—the Java interface expected to be implemented by the destination. |
|
n/a |
|
( |
|
The maximum number of messages that can exist for an asynchronous session, which have not yet been passed to the message listener. A value of When the number of messages reaches the specified value, the following occurs:
For multicast sessions, when a connection is stopped, messages will continue to be accumulated, but only until the specified maximum value is reached. Once this value is reached, messages will be discarded based on the overrun policy. |
|
|
|
( |
|
A string used by a client to specify, by header field references and property references, the messages it is interested in. Only messages whose header and property values match the selector are delivered |
Conditional expression using message properties, or message header |
Null |
|
( |
n/a |
Rarely used. |
|
n/a |
|
( |
|
The URL provider to be used by the |
Valid URL |
Null |
|
( |
|
For JCA-driven MDBs, identifies the resource adapter from which this MDB receives messages. |
n/a |
n/a |
|
( |
n/a |
Maps application roles in the |
n/a |
n/a |
|
( |
n/a |
Controls when MDBs start processing messages. When set to Set to false to defer message processing until after Oracle WebLogic Server opens its listen port. |
|
|
|
( |
|
Specifies whether a JMS topic subscription is |
|
|
|
( |
|
The name of the subscription if the message-driven bean is intended to receive messages published to a topic. You can set this property for durable or non-durable topic subscribers. |
n/a |
n/a |
|
n/a |
|
Sets the distribution mode for topic messages. See Configuring and Deploying MDBs Using JMS Topics.. |
|
|
|
( |
See trans-attribute |
Specifies an enterprise bean's transaction management type. For more information, see Configuring Transaction Management Strategy for an MDB. |
|
|
|
( |
import javax.ejb.TransactionAttribute
@TransactionAttribute(TransactionAttributeType.REQUIRED) |
Specifies how the container must manage the transaction boundaries when delegating a method invocation to an enterprise bean's business method. Note: f the bean is specified as using container-managed transaction demarcation, either the |
|
|
|
( |
|
The maximum duration for an EJB's container-initiated transactions, in seconds, after which the transaction is rolled back. See Configuring Transaction Management Strategy for an MDB. |
|
If the transaction time-out is not specified or is set to |
|
( |
|
Enables backwards compatibility for Oracle WebLogic Server version 8.1-style polling. |
|
False |
|
|
|
If AQ JMS is the JMS provider for the MDB and this property is set to true, synchronous polling uses the |
|
False |
|
|
|
When the JMS destination has no messages and synchronous polling is used for MDB, this property sets the message polling interval in milliseconds. When MDB interoperates with AQ JMS and minimizeAQSessions is set to true, you can avoid database connection usage bursts by setting this property to a value that is greater than 5000. This configuration randomly starts message polling when multiple MDBs are started.
|
> or = 0 (Integer) |
0 |
|
|
|
This property is only used when MDB interoperates with AQ JMS. When this property is set to true, it reduces database resource usage by dynamically closing AQ JMS sessions. |
|
False |