no-tx-datassource and required transaction type

[denis.etienne]

Hello,

In our project, we have defined a datasource using no-tx-datasource.

A client component does a remote call to a session bean method declared with

<trans-attribute>Required</trans-attribute>

In this session bean method, the datasource (no-tx) is obtained through JNDI, a connection is used to create a statement and call to s.executeUpdate is done.

We expected JBoss to be very noisy/angry about the Required-transaction method using a no-tx-datasource.

But nothing happened, can you explain ? please.
Thanks.
Denis.

[vickyk]

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

[denis.etienne]

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.