[
https://issues.apache.org/jira/browse/CAMEL-18833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650505#comment-17650505
]
Ephemeris Lappis commented on CAMEL-18833:
------------------------------------------
I understand that Camel 3.X requires changes, but could you confirm that any
blueprint context with transacted route must explicitly declare in its own code
a reference to the implementation of the Transaction Manager ?
The changes are not a lot of work, but they lead to add coupling to external
features that should not be a concern for Camel routes. If in the future Karaf
comes with alternative features that do not use Spring's Platform Transaction
Manager to handle transactions, all the Camel projects must be modified to
adapt themselves to an external context.
>From my point of view, this is not the best practice in an OSGi world...
Isn't another way to set a common Transaction policy out of the routes contexts
?
> 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)
