Eager validation for missing destroy methods [SPR-5602]

[spring-projects-issues]

Costin Leau opened SPR-5602 and commented

Currently, destroy methods are being discovered and invoked during destruction and any validation errors are only logged. The behaviour is different from init method which are validated at startup. An improvement would be to have the same behaviour for destroy methods as well - i.e. incorrect or missing methods would throw exceptions at startup (rather then at shutdown).

---

Affects: 2.5.6

Referenced from: commits bcf6f23

[spring-projects-issues]

Juergen Hoeller commented

Alright, we're eagerly validating destroy methods now. Wasn't quite as straightforward to change as I thought, since our disposable adapter needs to remain serializable when being put into a persistent session... That required quite some reworking of our DisposableBeanAdapter.

Juergen