Closed GoogleCodeExporter closed 9 years ago
I believe @PostConstruct is called directly on the bean instance by the spring
application context itself. Spring then adds the bean proxy wrapper which
applies the caching.
In short I don't believe things using @PostConstruct, or InitializingBean can
be cached in Spring. This is due to Spring's architecture, there is nothing we
can do in our library to address it.
Original comment by eric.dalquist
on 25 Oct 2010 at 4:39
Original issue reported on code.google.com by
var...@gmail.com
on 13 Oct 2010 at 9:42