Configure Borland Enterprise Server for the Example Message Driven Bean


Borland Enterprise Server contains an example MDB in the C:\BorlandEnterpriseServer\examples\ejb\mdb directory. The example consists of the MDB HelloBean.java and the client MdbClient.java. The same bean can be used to consume messages from both queues and topics.

The MDB is defined in the standard ejb-jar.xml deployment descriptor file. This file defines two EJBs, one named HelloEJBQueue and another named HelloEJBTopic. Both beans are implemented as the same class, com.borland.examples.ejb.mdb.HelloBean. This class can be used for this example without modification.

This example will not use XA transactions, therefore the deployment descriptor for the example MDB must be modified. The following two files must be modified to remove XA from the example:

 
C:\BorlandEnterpriseServer\examples\ejb\mdb\META-INF\ejb-jar.xml 
C:\BorlandEnterpriseServer\examples\ejb\mdb\META-INF\ejb-borland.xml 

In ejb-jar.xml, change the <trans-attribute> element of the deployment descriptor for the HelloEJBQueue bean. The attribute should be changed from "Required" to "NotSupported".

In ejb-borland.xml, the JMS Destination and Connection Factory JNDI names are pre-configured to use the XA Queue Connection Factory. Change the <connection-factory-name> element from serial://jms/xaqcf to serial://jms/qcf.


TIBCO Enterprise Message Service™ Application Integration Guide
Software Release 4.3, February 2006
Copyright © TIBCO Software Inc. All rights reserved
www.tibco.com