Question

I would like to rollback transaction not inside EJB but inside JSF managed bean. Inside EJB we can use SessionContext.setRollBackOnly() but what can I use in managed bean ?

@Stateless
@Local(AccountLocal.class)
public class AccountBean implements AccountLocal {

   public void test1() throws CustomException(){
      ...
   } 

   public void test2() throws CustomException(){
      ...
      throw new CustomException();
   }   

   public void test3() throws CustomException(){
      ...
   }

   public void all() throws CustomException(){
       test1();
       test2();
       test3();
   } 

}

In my managed bean :

@SessionScoped
public class LoginBean implements Serializable{

   public void test(){

      try{
         accountBean.test1();
         accountBean.test2();
         accountBean.test3();
      }catch(CustomException e){
         // WHAT HERE TO ROLLBACK TRANSACTION ?
      }      
    }    
}

EDIT : How can I ensure that if one of the test1, test2 or test3 rolls back, others will roll back too ?

I tested this code and accountBean.test1(); is validated even if accountBean.test2(); rolls back.

Could the solution be only to nest this 3 methods inside one EJB method ?

 @SessionScoped
public class LoginBean implements Serializable{

   public void test(){

      try{
         accountBean.all();
      }catch(CustomException e){
        ...
      }      
    }    
}

Answer 1

Transactions are automatically rolled back by the EJB container if an unchecked exception is thrown (note that JPA’s PersistenceException is such one). Your CustomException seems to be a checked exception. If changing it to extend RuntimeException as follows

public class CustomException extends RuntimeException {
    // ...
}

or creating a new one is not an option, then you need to set the @ApplicationException annotation on the class with the rollback attribute set to true.

E.g.

@ApplicationException(rollback=true)
public class CustomException extends Exception {
    // ...
}

Please note that the concrete problem has nothing to do with JSF. The service layer and managing transactions is completely outside the responsibility of JSF. It’s the responsibility of EJB instead. JSF should merely act as "view" in this perspective.

See also:

• JSF Service Layer
• Handling service layer exception in Java EE frontend method