Hi Karthik,
Yes it does. The reason is that very often multiple EJBs are enlisted in the same transaction. If your DataSource is non-TX then this is going to work if and only if all participants will share the same phisical databse connection. This basically means that you have to programm your EJBs accordingly and to pass
the same database connection from one bean to another. As with most of the EJBs one usually gets a new connection from the pool for every method call. In theory at least, using CMT should also imply that (for optimization reasons) the container will reuse the same connection throughout the entire transaction. In practice though it�s probably not going to work. However WebLogic will allow you setting TX-DataSources pretty easily, just enabling the
Honor Global Transactions when defining the DataSource. There are several reasons that might enforce your app to use non-TX drivers (when the underlying database doesn�t support distributed transactions, for example), but this should not be the case for any
EJB applications.
Regards.