This attribute determines whether the message-driven bean manages its own transactions, or whether the container manages transactions on behalf of the bean.
This attribute determines the JMS message selector that is used to select which messages the message bean receives.
JMSType='car' AND color='blue' AND weight>2500
The selector string can refer to fields in the JMS message header and fields in the message properties. Message selectors cannot reference message body values.
This attribute determines how the session acknowledges any messages it receives. This attribute applies only to message-driven beans that use bean-managed transaction demarcation (Transaction type is set to Bean).
As defined in the EJB specification, clients cannot use the Message.acknowledge() method to acknowledge messages. If a value of CLIENT_ACKNOWLEDGE is passed on the createxxxSession call, then messages are automatically acknowledged by the application server and the Message.acknowledge() method is not used.
The acknowledgement is sent when the message is deleted.
The message is deleted when the bean starts if the quality of service is set to Best effort nonpersistent. For all other qualities of service, the message is deleted when the bean completes.
This attribute determines whether the message bean uses a queue or topic destination.
This attribute determines whether a JMS topic subscription is durable or nondurable.
A nondurable subscriber can only be used in the same transactional context (for example, a global transaction or an unspecified transaction context) that existed when the subscriber was created. For more information about this context restriction, see Designing an enterprise application to use JMS.
This attribute specifies the JNDI name of the activation specification that is used to deploy this message-driven bean. This name must match the name of an activation specification that you define to WebSphere® Application Server.
Message linking allows the routing of messages to a specific message-driven bean in a deployment. Message linking allows message flow to be orchestrated between components in the same application.
For a message to be consumed and processed by a message-driven bean, the<message-destination-link> element must be defined in the deployment descriptor associated with the message-driven bean. The destination identified by the <message-destination-link> element corresponds to the logical destination.
When the <message-destination-ref> includes a <message-destination-link> element, messages will be consumed at that destination.
In order to get the message-driven bean to consume messages sent to a destination, you can declare a <message-destination-link> element in the deployment descriptor, or alternatively set it in the activation specification.