[
https://issues.apache.org/jira/browse/CAMEL-11665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320689#comment-16320689
]
ASF GitHub Bot commented on CAMEL-11665:
----------------------------------------
nicolaferraro commented on a change in pull request #2173: CAMEL-11665: Saga EIP
URL: https://github.com/apache/camel/pull/2173#discussion_r160746612
##########
File path:
camel-core/src/main/java/org/apache/camel/component/saga/SagaProducer.java
##########
@@ -0,0 +1,78 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.camel.component.saga;
+
+import org.apache.camel.AsyncCallback;
+import org.apache.camel.Exchange;
+import org.apache.camel.impl.DefaultAsyncProducer;
+import org.apache.camel.saga.CamelSagaService;
+import org.apache.camel.util.CamelContextHelper;
+
+/**
+ * A producer that finalizes the current saga.
+ */
+public class SagaProducer extends DefaultAsyncProducer {
+
+ private final boolean success;
+
+ private CamelSagaService camelSagaService;
+
+ public SagaProducer(SagaEndpoint endpoint, boolean success) {
+ super(endpoint);
+ this.success = success;
+
+ CamelSagaService sagaService =
endpoint.getCamelContext().hasService(CamelSagaService.class);
+ if (sagaService == null) {
+ sagaService =
CamelContextHelper.findByType(endpoint.getCamelContext(),
CamelSagaService.class);
+ }
+ if (sagaService == null) {
+ throw new IllegalStateException("Cannot find saga service: saga
producers can only be used within a saga");
+ }
+ this.camelSagaService = sagaService;
+ }
+
+ @Override
+ public boolean process(Exchange exchange, AsyncCallback callback) {
+ String currentSaga =
exchange.getIn().getHeader(Exchange.SAGA_LONG_RUNNING_ACTION, String.class);
+ if (currentSaga == null) {
+ exchange.setException(new IllegalStateException("Current exchange
is not bound to a saga context: cannot complete"));
+ callback.done(true);
+ return true;
+ }
+
+
+ camelSagaService.getSaga(currentSaga).thenApply(coordinator -> {
+ if (coordinator == null) {
+ throw new IllegalStateException("No coordinator found for saga
id " + currentSaga);
Review comment:
That's done on the `whenComplete` callback few lines below.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Define a saga DSL and implementation for long running actions
> -------------------------------------------------------------
>
> Key: CAMEL-11665
> URL: https://issues.apache.org/jira/browse/CAMEL-11665
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Nicola Ferraro
> Assignee: Nicola Ferraro
> Priority: Minor
>
> I'm trying to define a saga interface and DSL for Camel in order to support
> long running actions.
> I've done some experiments here:
> https://github.com/nicolaferraro/camel/blob/8ad4a4a264bbcd882507893e810a65578253caa4/camel-core/src/test/java/org/apache/camel/processor/SagaTest.java#L102-L146
> The experiment works with a in memory saga manager.
> It should be possible to switch to a proper "long running action coordinator"
> (e.g. the one proposed here
> https://github.com/jbosstm/microprofile-sandbox/blob/0009-LRA/proposals/0009-LRA/0009-LRA.md)
> once an implementation is ready.
> We can also think to provide our own implementation based on a shared
> transaction log, but it will be a "hard" task and it would not be compatible
> with other languages/frameworks, so the "spec" way should be preferable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
