You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/reference/asciidoc/dsl.adoc
+5
Original file line number
Diff line number
Diff line change
@@ -816,6 +816,11 @@ When you configure a sub-flow as a lambda, the framework handles the request-rep
816
816
Sub-flows can be nested to any depth, but we do not recommend doing so.
817
817
In fact, even in the router case, adding complex sub-flows within a flow would quickly begin to look like a plate of spaghetti and be difficult for a human to parse.
818
818
819
+
NOTE: Any sub-flow mappings end up with a `MessageChannel` connection between an original component as a producer (e.g. a `discardChannel` in the `MessageFilter`) and the first endpoint in the sub-flow as a consumer.
820
+
When sub-flow is started with a channel, an extra `bridge()` is placed between the mapping channel and this one to make the proper flow wiring.
821
+
When an existing `IntegrationFlow` bean is used as a subflow reference, there is no such a bridge in between since the framework can resolve the first channel from the flow bean.
822
+
This information is not available yet from inline subflows.
0 commit comments