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: modelling/command-handling/repository.md
+10
Original file line number
Diff line number
Diff line change
@@ -181,3 +181,13 @@ To enable it read in [Dbal Module Section](../../modules/dbal-support.md#documen
181
181
### - Event Sourcing Repository
182
182
183
183
Ecotone provides inbuilt Event Sourcing Repository, which will set up Event Store and Event Streams. To enable it read [Event Sourcing Section](../event-sourcing/).
184
+
185
+
## Using Multiple Repositories
186
+
187
+
By default Ecotone when we have only one Standard and Event Sourcing Repository registered, Ecotone will use them for our Aggregate by default. \
188
+
This comes from simplification, as if there is only one Repository of given type, then there is nothing else to be choose from. \
189
+
\
190
+
However, if we register multiple Repositories, then we need to take over the process and tell which Repository will be used for which Aggregate. 
191
+
192
+
* In case of [Custom Repositories](repository.md#set-up-your-own-implementation) we do it using **canHandle** method.
193
+
* In case of inbuilt Repositories, we should follow configuration section for given type
0 commit comments