0 Replies Latest reply on Jun 22, 2009 10:07 PM by Israel Fonseca

    Seam Transaction Management - Performance

    Israel Fonseca Apprentice

      Just a question about the seam global transactions. Isn't the transaction creation a heavy operation? I mean, tons of user at the same time creating two-transactions per request don't looks good for me, and not all operations in an application needs database access to justify the transaction creation.

      That's why currently I'm using the @Transactional attribute on my dao/business classes, like the BMT of ejbs. I think that's a good practice. But anyway...

      Well, Seam rlz, and the developers too, so that's why I think: Well, they should have a good reason to use it(global-transactions) as default. So that's what I'm asking, what reason is it?

      Thks in advance,