I know that one of the benefits of using
EJB is to offset the responsibility of transaction management to the EJB container, allowing developers to concentrate on business-specific features. At the moment, we are implementing a 3-tier system which consists of
JSP on the front end, stateless session beans on the app server as a facade to a data access layer, and of course Oracle database in the back end. The data access layer consists of
java classes that use
JDBC to manipulate the database. The stateless session bean layer allows distributed access to our JDBC calls in the data access layer. So my question is this: Since you can specify transactional attributes at the method level for stateless beans, would this imply that the EJB container will handle transactions for JDBC calls made from my data access layer? in other words, should I avoid using setAutoCommit(), commit(), and rollback() from my data access layer?
thanks,
SAF