[
https://issues.apache.org/jira/browse/CAMEL-25058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119955#comment-18119955
]
Claus Ibsen commented on CAMEL-25058:
-------------------------------------
Dependencies:
* CAMEL-25011 (PR #26869) must be merged first, on main and on each backport
line. Without it exchange copies (seda, wire tap, ...) lose their saga binding,
and saga:complete / saga:compensate after such a hop would fail.
* On 4.18.x the backport also needs CAMEL-24149 (SagaProducer reads the
exchange internal saga state first), which is on main and 4.22.x but not on
4.18.x.
* Follows CAMEL-24449, which applied the same rule to the Saga EIP.
_Claude Code on behalf of davsclaus_
> camel-saga - saga:complete and saga:compensate should only consult
> Long-Running-Action for a saga service that uses it
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25058
> URL: https://issues.apache.org/jira/browse/CAMEL-25058
> Project: Camel
> Issue Type: Improvement
> Components: eip
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
>
> CAMEL-24449 made the Saga EIP (SagaProcessor) consult the Long-Running-Action
> message header only when the configured CamelSagaService opts in via
> isLongRunningActionHeaderSupported() (LRA does, the in-memory service does
> not).
> The saga component producer (saga:complete / saga:compensate) still falls
> back to that header unconditionally when the exchange is not bound to a saga.
> Align it with SagaProcessor so the header is only consulted when the saga
> service supports it.
> This is a hardening / consistency change; it should be backported to the same
> lines as CAMEL-24449.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
