[
https://issues.apache.org/jira/browse/CAMEL-11665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16321846#comment-16321846
]
ASF GitHub Bot commented on CAMEL-11665:
----------------------------------------
davsclaus commented on issue #2173: CAMEL-11665: Saga EIP
URL: https://github.com/apache/camel/pull/2173#issuecomment-356859444
+1
----------------------------------------------------------------
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)
