@PostConstruct order in inheritance hierarchy is wrong (or at least not intuitive) [SPR-6094]

[spring-projects-issues]

Joern Barthel opened SPR-6094 and commented

• Define an abstract class Foo with an annotated init method.
• Define a concrete class Bar with an annotated init method.
• Define a bean instance of Bar.

After the bean instantiation the init method of Bar is called. Then the init method of Foo is called. This is probably the wrong way to do it since superclasses likely define/instantiate stuff children will depend on.

---

Affects: 2.5.6

Attachments:

• example.zip (1.58 kB)

Referenced from: commits d4c16e9

[spring-projects-issues]

Juergen Hoeller commented

I revisited the order of both @PostConstruct and @PreDestroy processing for 3.0 RC1: @PostConstruct is now being processed top-down (base class first), whereas @PreDestroy is getting processed bottom-up (subclass first).

Juergen