CMT NOT_SUPPORTED and REQUIRED transactional behavior

[antonio each]

Hi all

I have this scenario:

EJB1 have a method handler(List<UserDTO> users) annotated with : @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED). In this method I call other EJB2 method annoted with @TransactionAttribute(TransactionAttributeType.REQUIRED).

The goal is to have transaction only on single saveUser operation and not on complete users list.
If I have understod cmt transacation behavior the NOT SUPPORTED doesn't start a new transaction on handler() method,but create one when saveUser is called. is this right?

@Stateless
public class EJB1Facade implements IEJB1Facade{

   @EJB
   private IEJB2Facade ejb2facade;
   
   @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
   public void handler(List<UserDTO> users)
   {
       for(UserDTO user: users)
       {
          ejb2Facade.saveUser(user);
       }
   }

}


@Stateless
public class EJB1Facade implements IEJB1Facade{

   @TransactionAttribute(TransactionAttributeType.REQUIRED)
   public void saveUser(UserDTO user)
   {
        ........
        ........
   }

}

Thank you for suggests!