JBoss and JOnAS provide several vendor specific configuration options for Message Driven Beans. Example 2-12 and Example 2-13 provide configuration templates for the destination JNDI name, and for activation config properties.
Example 2-12. jboss.xml
<jboss>
<enterprise-beans>
<message-driven>
<ejb-name>Message Driven Bean Name</ejb-name>
...
<destination-jndi-name>Destination JNDI Name</destination-jndi-name>
...
<activation-config>
...
<activation-config-property>
<activation-config-property-name>Property Name</activation-config-property-name>
<activation-config-property-value>Property Value</activation-config-property-value>
</activation-config-property>
...
</activation-config>
...
</message-driven>
</enterprise-beans>
</jboss>Example 2-13. jonas-ejb-jar.xml
<jonas-ejb-jar>
<jonas-message-driven>
<ejb-name>Message Driven Bean Name</ejb-name>
...
<jonas-message-driven-destination>
<jndi-name>Destination JNDI Name</jndi-name>
</jonas-message-driven-destination>
...
<activation-config>
...
<activation-config-property>
<activation-config-property-name>Property Name</activation-config-property-name>
<activation-config-property-value>Property Value</activation-config-property-value>
</activation-config-property>
...
</activation-config>
...
</jonas-message-driven>
</jonas-ejb-jar>Note that the configuration schema contained by the <activation-config> element is identical for both JBoss and JOnAS.