Comments (2)
Actually I found out one issue with my tests. I will try to make a new test case.
from eventuate-tram-sagas.
Here is the updated version with the class which has the failing tests in my fork.
I looked around a little bit in the code and I noticed one difference between reactive and non-reactive, and it's in the ReactiveSagaManagerImpl.java file, line 182. There the data variable is passed to handleReply method, but it's coming from getSagaData(si) method call, while the data variable is also initialized separately on line 180. When I change line 182 to this, then these tests actually pass:
Mono<SagaActions<Data>> actions = Mono.from(getStateDefinition().handleReply(sagaType, sagaId, currentState, data, message));
I'm wondering though if there might be some reason for doing it like this or it's a bug, @cer
from eventuate-tram-sagas.
Related Issues (20)
- Support nested sagas HOT 3
- Investigate usage of SagaParticipantStubManager
- Parameter 3 of method sagaCommandDispatcherFactory in io.eventuate.tram.sagas.spring.participant.SagaParticipantConfiguration required a bean of type 'io.eventuate.tram.commands.consumer.CommandReplyProducer' that could not be found. HOT 1
- Support conditional sending of notifications
- Improve exception handling for local saga steps HOT 2
- Proposal: 'Global' failure handlers for failed participants
- Implement onStartingCompensation() method
- Investigate flakey test: shouldReject HOT 4
- Separate orchestrator and participant schema
- Use flyway to configure eventuate DB schema HOT 1
- fix auto-configuration loading in Spring Boot 3
- No qualifying bean of type 'io.eventuate.tram.sagas.orchestration.SagaInstanceFactory' available
- ERROR: relation "eventuate.saga_instance" does not exist HOT 39
- java.lang.RuntimeException: No method for io.eventuate.tram.messaging.common.MessageImpl@5ae52f04 HOT 5
- ReactiveSaga not started if i use PostgreSQL HOT 4
- Implement a SagaManagerListener HOT 2
- ReactiveSqlQueryRow expects boolean fields to be Int HOT 1
- When using reactive sagas, duplicate message detector causes consumer to crash on a duplicate HOT 2
- Consider defining a bean of type 'io.eventuate.tram.consumer.common.DuplicateMessageDetector' in your configuration
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eventuate-tram-sagas.