[
https://issues.apache.org/jira/browse/CAMEL-18833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18833.
---------------------------------
Resolution: Won't Fix
Camel 2 is EOL a long time ago, and migration to 3.x requires some changes.
> Transacted routes fail without explicit policy
> ----------------------------------------------
>
> Key: CAMEL-18833
> URL: https://issues.apache.org/jira/browse/CAMEL-18833
> Project: Camel
> Issue Type: Bug
> Components: came-core
> Affects Versions: 3.18.4
> Environment: The tests have been done assembling OSGi blueprints and
> deploying them as Karaf features on Karaf 4.4.2, either on Debian or Windows,
> running JDK 11.
> Reporter: Ephemeris Lappis
> Priority: Major
> Attachments: routes-k1.xml
>
>
> Transacted routes in blueprint doesn't work the way they worked with Camel
> 2.X.
> As it's documented with example, the "transacted" term in a route definition
> should be enough to enable transactions using the matching transaction
> manager. The attached blueprint seems to work adding an explicit
> "org.apache.camel.spring.spi.SpringTransactionPolicy" with a reference to the
> "PlatformTransactionManager". With Camel 2.X, and with the same installed
> features, these declarations aren't needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
