You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Balazs Zsoldos (Updated) (JIRA)" <ji...@apache.org> on 2012/04/04 13:52:23 UTC
[jira] [Updated] (ARIES-841) JPA PersistenceBundleManager does not
wait for TransactionSynchronizationRegistry to be available
[ https://issues.apache.org/jira/browse/ARIES-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Balazs Zsoldos updated ARIES-841:
---------------------------------
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
was:
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-480.
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
> 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
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira