You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/12/21 08:39:00 UTC
[jira] [Updated] (CAMEL-18833) camel-osgi - Transacted routes fail without explicit policy in OSGi blueprint
[ https://issues.apache.org/jira/browse/CAMEL-18833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-18833:
--------------------------------
Component/s: camel-karaf
(was: came-core)
> camel-osgi - Transacted routes fail without explicit policy in OSGi blueprint
> -----------------------------------------------------------------------------
>
> Key: CAMEL-18833
> URL: https://issues.apache.org/jira/browse/CAMEL-18833
> Project: Camel
> Issue Type: Bug
> Components: camel-karaf
> 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)