This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch fix/CAMEL-25058
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 8e7efed79cf4 CAMEL-25058: camel-saga - saga:complete and
saga:compensate only consult Long-Running-Action for a saga service that uses it
add 83c20f5550d3 CAMEL-25011: camel-core - Saga EIP: keep the saga of an
exchange in its copies (#26869)
add 6384bd0643d6 CAMEL-25058: camel-saga - saga:complete and
saga:compensate only consult Long-Running-Action for a saga service that uses it
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (8e7efed79cf4)
\
N -- N -- N refs/heads/fix/CAMEL-25058 (6384bd0643d6)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../camel/processor/SagaExchangeCopyTest.java | 101 +++++++++++++++++++++
.../org/apache/camel/support/AbstractExchange.java | 2 +
2 files changed, 103 insertions(+)
create mode 100644
core/camel-core/src/test/java/org/apache/camel/processor/SagaExchangeCopyTest.java
