Details
Description
Relevant description copied from CASTOR-1173
Ralf:
ATM we only have one global transaction manager which is ok for 1 jdo-conf, but if we load 2 different jdo-conf's they can have different definitions for transaction managers. IMO we will need to assign a ConnectionFactory with the transaction manager that will handle its transactions.
Werner:
I agree with Ralf that we need to re-assess some of the old assumptions in the light of multiple JDO configurations. This, imho, should be done in a separate Jira issue to be created.
Werner:
Actually, we should even reconsider whether the 1:m relation between transaction mode and databases instances is justified.
Issue Links
- depends upon
-
CASTOR-1173
Problem using JDOConfFactory and transaction demarcation specification.
-
- is depended upon by
-
CASTOR-1201
Seperate responsibility of DatabaseRegistry for database configuration and initialized database instances.
-
- relates to
-
CASTOR-1135
Refactor how JDBC connection factories are maintained
-