From a80c5fcfaf2786ab506d176e4a713ae983f9bfe5 Mon Sep 17 00:00:00 2001 From: Sviatoslav Hryb Date: Sat, 10 Apr 2021 20:38:27 +0300 Subject: [PATCH] Improve @EventListener documentation in reference manual Closes gh-26785 --- src/docs/asciidoc/core/core-beans.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/docs/asciidoc/core/core-beans.adoc b/src/docs/asciidoc/core/core-beans.adoc index 394db89706..10ec472c65 100644 --- a/src/docs/asciidoc/core/core-beans.adoc +++ b/src/docs/asciidoc/core/core-beans.adoc @@ -10652,7 +10652,7 @@ 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 public method of a managed +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: @@ -10793,7 +10793,7 @@ 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` of events +method above. If you need to publish several events, you can return a `Collection` or an `array` of events instead.