The steps we have outlined in this chapter assume that the MDB uses container-managed transactions. This section highlights configuration details related to this feature.The MDB developer did not code transaction logic into the MDB, and specified this fact to application server in the file ejb-jar.xml. Namely, the <transaction-type> attribute has the value Container. This fact has two consequences during deployment:
● JBoss 4.0.2 interprets this attribute value to indicate that the application requires an XA connection.
− If your application indeed requires container-managed XA transactions, then this interpretation is correct, and no changes are required.
− However, if your application does not use transactions at all, add this line to the <message-driven> element:XA Connection Factory
● When we configured the connection factories in the EMS server, we created XA connection factories (see Queues and Connection Factories).
− If your application indeed requires container-managed XA transactions, then this interpretation is correct, and no changes are required.
− However, if your application does not use transactions at all, you can instead create connection factories that do not support XA:
Copyright © TIBCO Software Inc. All Rights Reserved.