Claus Ibsen created CAMEL-25058:
-----------------------------------
Summary: 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
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)
