From d68dd17393c1b72970598d6561cb5e114b758e92 Mon Sep 17 00:00:00 2001 From: Max Romanovsky Date: Fri, 18 Mar 2016 19:13:36 +0300 Subject: [PATCH] Docs: Fixed misprint in AckRemoteApplicationEvent name --- docs/src/main/asciidoc/spring-cloud-bus.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/spring-cloud-bus.adoc b/docs/src/main/asciidoc/spring-cloud-bus.adoc index f43eaef..46bbba0 100644 --- a/docs/src/main/asciidoc/spring-cloud-bus.adoc +++ b/docs/src/main/asciidoc/spring-cloud-bus.adoc @@ -91,7 +91,7 @@ This trace shows that a `RefreshRemoteApplicationEvent` was sent from (acked) by `customers:9000` and `stores:8081`. To handle the ack signals yourself you could add an `@EventListener` -for the `AckRemoteAppplicationEvent` and `SentApplicationEvent` types +for the `AckRemoteApplicationEvent` and `SentApplicationEvent` types to your app (and enable tracing). Or you could tap into the `TraceRepository` and mine the data from there.