Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-537

Transaction demarcation does not affect session management for looked up EM.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • EJB 3.0 RC7 - FD
    • EJB 3.0 RC7 - FD
    • None
    • None

      Spoke over phone with this. JBMS does this:

      EntityManager session = ((EntityManager) ctx
      .lookup("java:/EntityManagers/mail"));

      And we have JBAOP TX tags. But introspection of the session reveals that the session is the same session for the entire thread. Despite transactional demarcation which of course causes problems for requires new.

      Desired behavior is that the EM facade should create different session under the covers and the transaction boundries are crossed regardless of the method of transactional control. (AOP Tx tags in this case)

      Please feel free to ask for more info.

            patriot1burke@gmail.com Bill Burke (Inactive)
            acoliver_jira Andrew Oliver (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: