Saga default processor type

Basic information

• Axon Framework version: 4.5
• JDK version: 15

I’m trying to better understand how sagas works and I’ve created three different projects to make some tests. I haven’t configure db to keep all in-memory. I discovered that the default configuration for sagas seems to be with subscribing processor instead the expected tracking processor.

Steps to reproduce

I wrote this simple saga:

@Saga
@Slf4j
public class TestSaga {
	@StartSaga
	@EndSaga
	@SagaEventHandler(associationProperty = "id")
	public void on(SampleEvent event) {
		log.debug("Test Saga handler. Event id: " + event.getId());
	}
}

This code print log only for live events, not for past events.

Then I tried simply adding the annotation @ProcessingGroup("MyTestSagaProcessor") and I noticed that it started to print debug log at startup for all past and live events (as expected).

Is this the intended behaviour?

[alezanola]

Although this might help, I am not certain how this deviates away from what you’re experiencing.

This resolved my problem: do not delete Db where tokens are saved even while testing (use Replay API instead).

Thanks again for your time and your help @smcvb.

[alezanola]

Test projects uploaded to this repository.

I suggest to replicate the steps described in my previous comment.

I have used IntelliJ IDEA to create the projects first and second. To start AxonServer and MongoDB simply run docker compose up in the root folder. I left a TODO on the commented @ProcessingGroup annotation.