Has anyone figured out how to get Jecks2.0 to do this?
When I run my JUnit tests it appears Jencks2.0 is not using the transaction that was already started. However, when that initial transaction rolls back and the next test method is executed everything seems to work fine.
Is there a easy way to either force Jencks to use the initial transaction, or drop the initial transaction and create a new one?
I'm really struggling with this issue, so any help would be greatly appreciated.
Thanks,
Bob
I'm using Jencks2.0\Junit\Oracle\Ant\Eclipse in a multiple data source configuration.
Mad Andy wrote:
I want to use an Outbound JDBC through Jencks but the transaction is started and managed outside. It seems to me that in this case Jencks' transaction manager is not joining the transaction.
Is there a way to make Jenck's transaction manager joining an existing transaction on the current thread rather than starting its own?
Thanks - Andy Schaefer
