Skip to content

Commit 3bf7dab

Browse files
committed
Set right version for link
Set right version for link
1 parent 27dfdad commit 3bf7dab

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/reference/modules/ROOT/pages/command-routes.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ There are decorators present for the `CapabilityDiscoveryMode`, providing two ad
2424
2525
The `Registration`, `DiscoveryClient` and `CapabilityDiscoveryMode` are arguably the heart of the `SpringCloudCommandRouter`. There are, however, a couple of additional things you can configure for this router, which are the following:
2626
27-
- `RoutingStrategy` - The component in charge of deciding which of the nodes receives the commands consistently. By default, a `AnnotationRoutingStrategy` is used (see link:https://docs.axoniq.io/axon-framework-reference/4.11/axon-framework-commands/infrastructure/#DistributedCommandBus[Distributing the Command Bus] for more).
27+
- `RoutingStrategy` - The component in charge of deciding which of the nodes receives the commands consistently. By default, a `AnnotationRoutingStrategy` is used (see link:https://docs.axoniq.io/axon-framework-reference/4.12/axon-framework-commands/infrastructure/#DistributedCommandBus[Distributing the Command Bus] for more).
2828
2929
- A `ServiceInstance` filter - This `Predicate` is used to filter out `ServiceInstance` retrieved through the `DiscoveryClient`. For example, it allows the removal of instances which are known to not handle any command messages. This might be useful if you have several services within the Spring Cloud Discovery Service set up, which you do not ever want to take into account for command handling.
3030

0 commit comments

Comments
 (0)