From bcc6171a72b0a7fa3e21919f2c2fc7b3daf36a30 Mon Sep 17 00:00:00 2001 From: Sam Brannen Date: Tue, 13 Apr 2021 11:21:56 +0200 Subject: [PATCH] Polish contribution See gh-26785 --- src/docs/asciidoc/core/core-beans.adoc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/docs/asciidoc/core/core-beans.adoc b/src/docs/asciidoc/core/core-beans.adoc index 10ec472c65..c9ebdb478e 100644 --- a/src/docs/asciidoc/core/core-beans.adoc +++ b/src/docs/asciidoc/core/core-beans.adoc @@ -10652,9 +10652,8 @@ architectures that build upon the well-known Spring programming model. [[context-functionality-events-annotation]] ==== Annotation-based Event Listeners -As of Spring 4.2, you can register an event listener on any method of a managed -bean by using the `@EventListener` annotation. The `BlockedListNotifier` can be rewritten as -follows: +You can register an event listener on any method of a managed bean by using the +`@EventListener` annotation. The `BlockedListNotifier` can be rewritten as follows: [source,java,indent=0,subs="verbatim,quotes",role="primary"] .Java @@ -10792,9 +10791,9 @@ method signature to return the event that should be published, as the following NOTE: This feature is not supported for <>. -This new method publishes a new `ListUpdateEvent` for every `BlockedListEvent` handled by the -method above. If you need to publish several events, you can return a `Collection` or an `array` of events -instead. +The `handleBlockedListEvent()` method publishes a new `ListUpdateEvent` for every +`BlockedListEvent` that it handles. If you need to publish several events, you can return +a `Collection` or an array of events instead. [[context-functionality-events-async]] -- GitLab