So I’ve done a little more digging and found a few more pieces in the docs that I am hoping to get clarification on. In the docs for implementing a Saga it says:
“Sagas are managed by a single event processor (Tracking or Subscribing), which is dedicated to dealing with events for that specific saga type.”
- Implementation
So this had me wondering if the SagaManager creates it’s own event processor, and therefore even if you use the @ProcessingGroup annotation, the processing group for the saga would go to a different event processor than the Event Handling Component.
If I am understanding this correctly (which I very well may not), I think that my event handler configuration would look something like the following:
I am assuming this is because of how the Event Processor for a Saga must be different than a normal event processor, in that it needs to find an association property to determine which instance(s) of a Saga should handle an event. As such, you can’t really put them in the same Event Processor, and therefore you cannot order them.
Am I understanding this correctly?
If so, I would also like to clarify that there is no way to use any of the “assignment rules” mentioned in this note to be able to configure both handlers in the same processing group?
‘As a Saga is a type of event handler, it is part of an Event Processor. Without defining any assignment rules, a Saga’s processor name equals the Saga name appended with “Processor”’
- Configuring a Saga