This content has been marked as final. Show 2 replies
We expected JBoss to be very noisy/angry about the Required-transaction method using a no-tx-datasource.
Why would you expect this ?
In JEE can't you have a EJB calling the DAO which is getting the connection from the custom connection pool (a properiotary one) ?
It is ok , I dont find any flaw here
In my opinion, datasource knows the context of the call (ie Session Bean with Transaction Type=Required) but this datasource is not capable of handling transaction, that's why I expected JBoss to warn us.
But I may miss some point.