CMT NOT_SUPPORTED and REQUIRED transactional behavior
posted 5 years ago
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?