[
https://issues.apache.org/jira/browse/CAMEL-25058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119873#comment-18119873
]
Claus Ibsen commented on CAMEL-25058:
-------------------------------------
PR: https://github.com/apache/camel/pull/26941 (depends on
https://github.com/apache/camel/pull/26869 / CAMEL-25011). To be backported to
4.22.x and 4.18.x like CAMEL-24449.
_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)
