Croway opened a new pull request, #30166:
URL: https://github.com/apache/camel/pull/30166

   JIRA: [CAMEL-27021](https://issues.apache.org/jira/browse/CAMEL-27021)
   
   - `transacted()` without a policy made a local `JdbcTransactionManager` 
whenever `findSingleByType(PlatformTransactionManager)` returned null. That is 
also the case with two or more transaction managers, so with one `DataSource` 
the route started and used a new transaction manager, not one of the 
application's.
   - The local transaction manager is now made only when the registry has no 
transaction manager (CAMEL-26851, not released yet). With two or more, the 
route fails to start with `NoSuchBeanTypeException`, as in 4.23.0, and the 
message now says how many were found (`Found 2 beans for: 
org.springframework.transaction.PlatformTransactionManager in the registry, 
...`) instead of "No bean could be found".
   - Change in `AbstractPolicyReifier`. The transactional client page says what 
to do with two or more transaction managers (refer to a 
`SpringTransactionPolicy`).
   
   Tests: `SqlTransactedTwoTransactionManagersTest` (camel-sql). Two tests fail 
before (with one `DataSource` the route starts and binds a new 
`transactionManager`; with two the message says no bean was found) and pass 
after. Two controls pass before and after: one transaction manager is used, and 
a `SpringTransactionPolicy` picks one of two. The transacted and policy tests 
of camel-core, camel-spring-xml, camel-test-spring-junit6 and camel-sql 
(`*Transact*`, `*TXManager*`, `Policy*Test`: 167 tests) pass with the fix.
   
   No upgrade guide entry: the local transaction manager is not released, and 
4.23.0 failed in this case too.
   
   _Claude Code on behalf of Federico Mariani_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to