Uploaded image for project: 'Aries'
  1. Aries
  2. ARIES-841

JPA PersistenceBundleManager does not wait for TransactionSynchronizationRegistry to be available

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • jpa-2.0.0
    • JPA
    • None
    • Apache Aries Transaction Manager and JPA

    Description

      If a persistence unit uses JTA as transaction type it would be useful if the Aries JPA would take that PU live only when TransactionSynchronizationRegistry OSGI service is available. Without that we have to take care that the aries transaction* bundles are before the aries JPA bundles in the starting queue.

      Please note that this issue is similar to ARIES-840.

      Steps to reproduce:

      • Check out https://guest:guest@source.everit.biz:443/svn/everit-osgi/trunk
      • Run "mvn clean install". As a result you will see that hibernate tests run from the hibernate/tests/core project
      • Edit the hibernate/tests/core/pom.xml file: Take the "org.apache.aries.transaction.manager" dependency to the end of the dependency list
      • Run the "mvn clean install" again. As now the DataSourceFactory will be available later than the aries.jpa.container is initialized the solution will not work

      Attachments

        Activity

          People

            cschneider Christian Schneider
            balazs.zsoldos Balazs Zsoldos
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: