khj68 c0b71f8999 Improve Javadoc of ApplicationEvents to clarify preferred usage ...

This commit reorders and clarifies the usage instructions for
ApplicationEvents to:

1. Recommend method parameter injection as the primary approach, since
   ApplicationEvents has a per-method lifecycle
2. Clarify that ApplicationEvents is not a general Spring bean and
   cannot be constructor-injected
3. Explicitly state that field injection is an alternative approach

This addresses confusion where developers expect ApplicationEvents to
behave like a regular Spring bean eligible for constructor injection.

See gh-35297
Closes gh-35335

Signed-off-by: khj68 <junthewise@gmail.com>

2025-08-20 16:31:41 +02:00

..

src

Improve Javadoc of ApplicationEvents to clarify preferred usage

2025-08-20 16:31:41 +02:00

.springBeans

Support classes AND locations in @ContextConfiguration

2014-04-01 19:45:56 +02:00

spring-test.gradle

Revise TestConventions to retain existing JUnit Platform options

2025-04-25 13:38:18 +02:00