Luca Burgazzoli created CAMEL-17129:
---------------------------------------
Summary: core: add a better way to configure capabilities such as
tx, saga, etc.
Key: CAMEL-17129
URL: https://issues.apache.org/jira/browse/CAMEL-17129
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Luca Burgazzoli
Fix For: 3.x
While working on the YAML DSl, I've noticed that a route like:
{code:yaml}
- from:
uri: "direct:start"
steps:
- saga:
propagation: "MANDATORY"
completion-mode: "MANUAL"
steps:
- to: "direct:something"
- to: "mock:result"
{code}
Gets re-wired to be something like:
{code:yaml}
- from:
uri: "direct:start"
steps:
- saga:
propagation: "MANDATORY"
completion-mode: "MANUAL"
steps:
- to: "mock:result"
- to: "direct:something"
{code}
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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
