Call Lifecycle.stop()
for already started beans on failed refresh [SPR-15468]
#20028
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
type: enhancement
A general enhancement
Milestone
Bill Chen opened SPR-15468 and commented
Currently,
Lifecycle.stop()
is documented not to be called if refresh failed. However, this makes lifecycle process really asymmetrical (especially when refresh failed due to an exception thrown from Lifecycle.start()).Can an option be added to call
Lifecycle.stop()
on already started beans?No further details from SPR-15468
The text was updated successfully, but these errors were encountered: