2 Replies Latest reply on Nov 11, 2009 4:21 PM by Francisco Jose Peredo Noguez

    Why transactional?

    Nicklas Karlsson Master

      4.2.2.GA, POJO:s, WAR, JPA/JTA.

      I have a method that adds a row to collection in a managed entity.

      The problem is that if I load the entity and invoke the method, everything is fine and the row is added, but if I make a new order, persist it, and then call the method, Seam tries to flush the changes (failing since there is information missing in the row at that time). And I have no @Transactional stuff there. How is it determined if the Work should be done in a transaction or not?