[
https://issues.apache.org/jira/browse/CAMEL-15724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472015#comment-17472015
]
Romain Manni-Bucau commented on CAMEL-15724:
--------------------------------------------
FYI [https://github.com/apache/camel/pull/6705] but reviewing the usage I think
camel-jta and camel-cdi don't need to be linked together at all, it looks just
a DSL thing and it is not in CDI scope in general (actually it is misleading
since in a lot of cases you don't want this but a resource local kind of txmgr
which is not provided by this integration directly) so maybe something to plan
to drop/deprecate?.
> Decouple camel-cdi from JTA
> ---------------------------
>
> Key: CAMEL-15724
> URL: https://issues.apache.org/jira/browse/CAMEL-15724
> Project: Camel
> Issue Type: Task
> Components: camel-cdi
> Reporter: Romain Manni-Bucau
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.15.0
>
>
> JTA is fully optional and when undesired it makes camel-cdi module unusable.
> Would be great to keep camel-cdi only depending on CDI and have a jta
> integration either in a new module or in a jta module.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
