parent
a80c5fcfaf
commit
bcc6171a72
|
|
@ -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
|
||||
<<context-functionality-events-async, asynchronous listeners>>.
|
||||
|
||||
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]]
|
||||
|
|
|
|||
Loading…
Reference in New Issue