glassfish
  1. glassfish
  2. GLASSFISH-138

Need actual EntityManager and not EntityManagerWrapper

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 9.0pe
    • Fix Version/s: 9.0pe
    • Component/s: ejb_container
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      138

      Description

      The EntityManager that is injected into a session bean is of type
      EntityManagerWrapper.

      However, since I need special functionality [Hibernate QL], I would like to get
      access to the delegate EntityManager somehow?

      Is there any way to:
      1- Make getDelegate public [ugly solution]
      2- Have the session bean have an injected entitymanager corresponding to the
      delagate instead of the wrapper?

        Activity

        Hide
        marina vatkina added a comment -

        Ken, please look

        Show
        marina vatkina added a comment - Ken, please look
        Hide
        marina vatkina added a comment -

        Reassigned to ken

        Show
        marina vatkina added a comment - Reassigned to ken
        Hide
        ksak added a comment -

        This is an EJB 3.0 spec issue that is being discussed in the expert group.
        SUN's implementation will not be exposing a proprietary way to access the
        underlying physical EntityManager object. Using the current functionality it
        should be possible set provider specific properties at the EntityManagerFactory
        level via persistence.xml. That would not specifically allow EntityManager
        level granularity for setting provider specific behavior, which is one reason
        the expert group is still discussing the matter. Please send additional
        feedback on this issue directly to the ejb 3.0 expert group at
        ejb3-pfd-feedback@sun.com.

        Show
        ksak added a comment - This is an EJB 3.0 spec issue that is being discussed in the expert group. SUN's implementation will not be exposing a proprietary way to access the underlying physical EntityManager object. Using the current functionality it should be possible set provider specific properties at the EntityManagerFactory level via persistence.xml. That would not specifically allow EntityManager level granularity for setting provider specific behavior, which is one reason the expert group is still discussing the matter. Please send additional feedback on this issue directly to the ejb 3.0 expert group at ejb3-pfd-feedback@sun.com.

          People

          • Assignee:
            ksak
            Reporter:
            egulatee
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: