You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating this issue per Juergen's request:
because support for @PostConstruct is implemented using a BeanPostProcessor, the BPP.postProcessBeforeInitialization method is invoked after the actual initialization method that has the annotation. This has always been the case since support for JSR-250 was added I think, but no issue was ever created to make sure to track this deficiency.
Added a simple test case that shows the described behavior,
I've finally addressed this through re-ordering our post-processors: Internal ones simply kick in after regular ones now. That seems to work fine in all common cases.
Joris Kuipers opened SPR-6066 and commented
Creating this issue per Juergen's request:
because support for
@PostConstruct
is implemented using a BeanPostProcessor, the BPP.postProcessBeforeInitialization method is invoked after the actual initialization method that has the annotation. This has always been the case since support for JSR-250 was added I think, but no issue was ever created to make sure to track this deficiency.Added a simple test case that shows the described behavior,
Affects: 2.5.6, 3.0 M4
Attachments:
Referenced from: commits 7428014, fcaf692, c495cbb
The text was updated successfully, but these errors were encountered: