Doc: aop proxy interceptor doesn't wrap bean's init-method [SPR-2740]

[spring-projects-issues]

Dmitry V. Zemnitskiy opened SPR-2740 and commented

In our application we use well adopted architecture with business manager implementing business interface.
Transaction proxy interceptor is wrapped around manager implementation to add declarative support of
hibernate transactions.

In the same business manager which is application level singleton we wished to use init-method to check
database and populate it with default bootstrap data (default system account, lookup data, etc).

What we noticed, is the transacton interceptor didn't wrap init-method even if it is included in proxy interface.

We solved this problem by creating another application level bean with init method which calls manager's method
when initialized.

I think it is relatively common usecase and spring aop should either intercept init-methods as well, or if it's impossible
for some architectural reason, just state this explicitly in spring documentation (lifecycle section or aop section).

Thanks, Dima

---

Affects: 2.0 RC4

[spring-projects-issues]

Juergen Hoeller commented

This is actually the expected behavior: A target bean is fully created first, then the AOP proxy with its interceptor chain is applied. Note that, if the target bean and the proxy are defined separately, you can even talk to the raw target object, bypassing the proxy. Hence, it would be very inconsistent to apply the interceptors to the init method, since that would couple the lifecycle of the target object with its proxy/interceptors, and leave strange semantics when talking to the raw target object directly.

As a consequence, I take this as an indication that we need to explictly state this in our documentation.

In any case, thanks for pointing this out!

Juergen

[spring-projects-issues]

Rick Evans commented

Fixed. Thanks for bringing this up.