DAO and CMT config...

Question

Hi.
          I am using WLS 8.1 sp2 . I have a stateless session bean that uses a DAO for database access. It appears that the DAO is not participating in the transaction. Here is a very simple example, here is my slsb method:
          public String doTransaction(int id, String name, String description)
          throws RemoteException
          //Call two methods, do the first to write a record, then
          //call setRollbackOnly to see if it is rolled back.
          try
          StoreDAO storeDAO = StoreDAOFactory.getDAO();
          storeDAO.saveT1(id, name);
          //I FORCE THIS CALL TO THROW AN EXCEPTION
          storeDAO.saveT2(id, description);
          catch( Exception e)
          ctx.setRollbackOnly(); //<-- saveT1 is NOT rolled back
          System.out.println("Ok, the rollbackonly was called");
          return e.getMessage();
          return "ok";
          Here is ejb-jar.xml as it pertains to this method:
          <container-transaction>
          <method>
          <ejb-name>ShoppingCartBean</ejb-name>
          <method-name>doTransaction</method-name>
          </method>
          <trans-attribute>RequiresNew</trans-attribute>
          </container-transaction>
          I force saveT2 to throw an exception right away, so the transaction will be rolled back, but the data that was written to the database during the saveT1 call is not rolled back.
          I obtain the database connection in the DAO by doing a JNDI lookup for the datasource that I configured with weblogic.
          Any Ideas?

Answer 1

How is the DataSource configured? Is is a JDBCDataSource or a
          JDBCTxDataSource? If it isn't the latter, it isn't transactional and it will
          not be enlisted in the transaction started by the container.
          Bill
          "david kessler" <[email protected]> wrote in message
          news:15207409.1107277453717.JavaMail.root@jserv5...
          > Hi.
          >
          > I am using WLS 8.1 sp2 . I have a stateless session bean that uses a DAO
          > for database access. It appears that the DAO is not participating in the
          > transaction. Here is a very simple example, here is my slsb method:
          >
          > public String doTransaction(int id, String name, String description)
          > throws RemoteException
          > {
          > //Call two methods, do the first to write a record, then
          > //call setRollbackOnly to see if it is rolled back.
          > try
          > {
          > StoreDAO storeDAO = StoreDAOFactory.getDAO();
          > storeDAO.saveT1(id, name);
          > //I FORCE THIS CALL TO THROW AN EXCEPTION
          > storeDAO.saveT2(id, description);
          > }
          > catch( Exception e)
          > {
          > ctx.setRollbackOnly(); //<-- saveT1 is NOT rolled back
          > System.out.println("Ok, the rollbackonly was called");
          > return e.getMessage();
          > }
          > return "ok";
          > }
          >
          > Here is ejb-jar.xml as it pertains to this method:
          >
          > <container-transaction>
          > <method>
          > <ejb-name>ShoppingCartBean</ejb-name>
          > <method-name>doTransaction</method-name>
          > </method>
          > <trans-attribute>RequiresNew</trans-attribute>
          > </container-transaction>
          >
          > I force saveT2 to throw an exception right away, so the transaction will
          > be rolled back, but the data that was written to the database during the
          > saveT1 call is not rolled back.
          >
          > I obtain the database connection in the DAO by doing a JNDI lookup for the
          > datasource that I configured with weblogic.
          >
          > Any Ideas?