[
https://issues.apache.org/jira/browse/CAMEL-21791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17986458#comment-17986458
]
Claudio Miranda commented on CAMEL-21791:
-----------------------------------------
I could make it working with only the {{transacted}} property, so the
{{transactional.id}} is calculated by using the endpoint.id + routeId, so no
need for the prefixId, this is enough to have a transactional kafka producer
per route.
The application.properties can contain the
{{camel.component.kafka.transacted=true}} or in the endpoint parameters.
I will provide the branch with the tests, documentation and quickstarts.
> camel-kafka - Make kafka transactions more easier to use
> --------------------------------------------------------
>
> Key: CAMEL-21791
> URL: https://issues.apache.org/jira/browse/CAMEL-21791
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Reporter: Claus Ibsen
> Assignee: Claudio Miranda
> Priority: Major
> Fix For: 4.x
>
>
> We should make it possible to use by setting transacted=true, and allow
> optional transaction.id prefix (need to generate uid). See for example how
> spring-kafka does it.
> Also it may be that we need to have support for invoking being/commit/abort
> transaction methods, and if we can integrate this with spring-transaction /
> jta via Camel transacted EIP.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
