OpenJPA
  1. OpenJPA
  2. OPENJPA-2234

EntityManager instance creation needs TX activity

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.3.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      - JDK 1.5
      - Spring 3.1.1.RELEASE
      - Spring Data JPA 1.1 GA (issue confirmed on version 1.0.3)
      - Atomikos 3.7.0
      - OpenJPA 2.0.1
      - DB2 9.7

      Description

      While working with Spring Data, we came across a potential bug in OpenJPA.

      The bug was provoked by a query lookup module in Spring Data JPA, but it has its roots in AbstractBrokerFactory class, which seems to require transaction existence in order to create EntityManager (which is contrary to JPA spec).

      I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug here.

      I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here.

      All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec.

        Activity

        Mark Struberg made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Rick Curtis made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Rick Curtis made changes -
        Fix Version/s 2.3.0 [ 12319463 ]
        Rick Curtis made changes -
        Resolution Invalid [ 6 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        Assignee Rick Curtis [ curtisr7 ]
        Rick Curtis made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Invalid [ 6 ]
        Erik Kis made changes -
        Description While working with Spring Data, we came across a potential bug in OpenJPA.

        The bug was provoked by a query lookup module in Spring Data JPA, but it has it roots in AbstractBrokerFactory class, which seems to require transaction existence in order to create EntityManager (which is contrary to JPA spec).

        I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug here.

        I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here.

        All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec.
        While working with Spring Data, we came across a potential bug in OpenJPA.

        The bug was provoked by a query lookup module in Spring Data JPA, but it has its roots in AbstractBrokerFactory class, which seems to require transaction existence in order to create EntityManager (which is contrary to JPA spec).

        I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug here.

        I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here.

        All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec.
        Erik Kis made changes -
        Description While working with Spring Data, we came across a potential bug in OpenJPA.

        The bug was provoked by a query lookup module in Spring Data JPA, but it has it roots in AbstractBrokerFactory class, which seems to requires transaction existence in order to create EntityManager (which is contrary to JPA spec).

        I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug here.

        I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here.

        All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec.
        While working with Spring Data, we came across a potential bug in OpenJPA.

        The bug was provoked by a query lookup module in Spring Data JPA, but it has it roots in AbstractBrokerFactory class, which seems to require transaction existence in order to create EntityManager (which is contrary to JPA spec).

        I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug here.

        I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here.

        All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec.
        Erik Kis made changes -
        Field Original Value New Value
        Description While working with Spring Data, we came across a potential bug in OpenJPA.

        The bug was provoked by a query lookup module in Spring Data JPA, but it has it roots in AbstractBrokerFactory class, which seems to requires transaction existence in order to create EntityManager (which is contrary to JPA spec).

        I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug _here_.

        I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here.

        All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec.
        While working with Spring Data, we came across a potential bug in OpenJPA.

        The bug was provoked by a query lookup module in Spring Data JPA, but it has it roots in AbstractBrokerFactory class, which seems to requires transaction existence in order to create EntityManager (which is contrary to JPA spec).

        I have already been in touch with Spring Data JPA author (where I filed a bug against Spring Data JPA) who actually pointed me to file a bug here.

        I have extensively documented my findings on this thread (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager), so I'll rather post the link, instead of repeating the whole thing here.

        All that being said, I am not entirely sure what actually happened and am no authority whatsoever on JPA spec.
        Erik Kis created issue -

          People

          • Assignee:
            Rick Curtis
            Reporter:
            Erik Kis
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development