[ https://issues.apache.org/jira/browse/ARIES-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved ARIES-841. --------------------------------------- Resolution: Fixed Assignee: Christian Schneider Fix Version/s: jpa-2.0.0 In Aries JPA 2.0.0 the EntityManagerFactory service for JTA persistence units will only be created if PersistenceProvider, TransactionManager and DataSource are available and be closed if one of this goes away. > JPA PersistenceBundleManager does not wait for > TransactionSynchronizationRegistry to be available > ------------------------------------------------------------------------------------------------- > > Key: ARIES-841 > URL: https://issues.apache.org/jira/browse/ARIES-841 > Project: Aries > Issue Type: Bug > Components: JPA > Environment: Apache Aries Transaction Manager and JPA > Reporter: Balazs Zsoldos > Assignee: Christian Schneider > Fix For: jpa-2.0.0 > > > 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:gu...@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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)