posted 16 years ago
The only option here would be to declare the same MDB as multiple MDB's in the deployment descriptor
For example
i.e
<message-driven>
<ejb-name>DMProcessorMDB1</ejb-name>
<ejb-class>com.bt.dm.ejb.DMProcessorMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<resource-ref>
<res-ref-name>jdbc/DSRef</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</message-driven>
<message-driven>
<ejb-name>DMProcessorMDB2</ejb-name>
<ejb-class>com.bt.dm.ejb.DMProcessorMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<resource-ref>
<res-ref-name>jdbc/DSRef</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</message-driven>
where DMProcessorMDB1 and DMProcessorMDB2 are the pointing to the same MDB Class