Transaction Management with JBoss Seam + JPA (Hibernate) like Spring Framework

I'm a fan of using Spring framework for all my projects, but unfortunately on my current project, I have to add a module to an existing app already developed using JBoss Seam EJB3 and Hibernate, so this is what I did to work with the same model of ServiceImpl that Spring uses

This is the DAO (Existing) - I just added the save method
@Name("purchaseDao") @AutoCreate @Stateless @TransactionAttribute(TransactionAttributeType.REQUIRED) @TransactionManagement(TransactionManagementType.CONTAINER) public class PurchaseDAO_EJB3_Impl implements PurchaseDAO { private static Log log = LogFactory.getLog(PurchaseDAO_EJB3_Impl.class); @PersistenceContext(type = PersistenceContextType.TRANSACTION) private EntityManager em; .... public void save(Purchase instance) { log.debug("Saving "+instance); em.persist(instance); log.debug("Saved"); } } And this will be My Service (I will not include the Interfaces)
@Name("enrollmentDetailsServiceBean") @AutoCreate public class EnrollmentDetailsServiceImpl implements IEnrollmentDetailsService { private static Logger log = Logger.getLogger(EnrollmentDetailsServiceImpl.class); @In("purchaseDao") private PurchaseDAO purchaseDAO; /* * Service method which will handle the Transaction */ @Transactional(TransactionPropagationType.REQUIRED) public Boolean saveEnrollmentDetails(EnrollmentDetails enrollmentDetails) throws Exception { Boolean result = false; try{ log.debug("Transform "+enrollmentDetails+" into POJOs"); Purchase purchase = Transformer.transform(enrollmentDetails); log.debug("Start saving PURCHASE, PURCHASE_MODULE & TRANSACTION"); purchaseDAO.save(purchase); log.warn("Insert another POJO (which already exists on the table) to break this thing :P"); Purchase purchase2 = new Purchase(); purchaseDAO.save(purchase2); log.debug("Inserts completed!"); result = true; }catch (Exception ex) { log.error("Error while saving EnrollmentDetails into DB: PURCHASE, PURCHASE_MODULE, TRANSACTION",ex); throw ex; } return result; } }
By doing this we have the same model of Tx Management - Just by adding the 1 annotation to the method!!! Cool Isn't it?
Also, in case that you want to make your Tx ReadOnly, just add this annotation to your method (also)

org.jboss.seam.annotations.ReadOnly

Unfortunately the documentation for JBoss Seam is really poor on this aspect, so If anybody finds anything that could be improved, please let me know)