Commit baef6c80 authored by Stephane Nicoll's avatar Stephane Nicoll

Merge pull request #21692 from making

* pr/21692:
  Fix event name in documentation

Closes gh-21692
parents e936e9aa 0cd526c2
...@@ -313,7 +313,7 @@ Application events are sent in the following order, as your application runs: ...@@ -313,7 +313,7 @@ Application events are sent in the following order, as your application runs:
. An `ApplicationStartedEvent` is sent after the context has been refreshed but before any application and command-line runners have been called. . An `ApplicationStartedEvent` is sent after the context has been refreshed but before any application and command-line runners have been called.
. An `AvailabilityChangeEvent` is sent right after with `LivenessState.CORRECT` to indicate that the application is considered as live. . An `AvailabilityChangeEvent` is sent right after with `LivenessState.CORRECT` to indicate that the application is considered as live.
. An `ApplicationReadyEvent` is sent after any application and command-line runners have been called. . An `ApplicationReadyEvent` is sent after any application and command-line runners have been called.
. An `LivenessState` is sent right after with `ReadinessState.ACCEPTING_TRAFFIC` to indicate that the application is ready to service requests. . An `AvailabilityChangeEvent` is sent right after with `ReadinessState.ACCEPTING_TRAFFIC` to indicate that the application is ready to service requests.
. An `ApplicationFailedEvent` is sent if there is an exception on startup. . An `ApplicationFailedEvent` is sent if there is an exception on startup.
The above list only includes ``SpringApplicationEvent``s that are tied to a `SpringApplication`. The above list only includes ``SpringApplicationEvent``s that are tied to a `SpringApplication`.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment