Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Unknown
Description
While working on the YAML DSl, I've noticed that a route like:
- from: uri: "direct:start" steps: - saga: propagation: "MANDATORY" completion-mode: "MANUAL" steps: - to: "direct:something" - to: "mock:result"
Gets re-wired to be something like:
- from: uri: "direct:start" steps: - saga: propagation: "MANDATORY" completion-mode: "MANUAL" steps: - to: "mock:result" - to: "direct:something"
So in fact any output is moved to the saga outputs.
This happen because the saga is supposed to be a top level only feature and to be applied to the entire route (same for transacted).
The model should have a a separate definition for route configurations so you can configure saga, tx, onException et all there only and not later in the regular route