Simple concept question: intercept multi-thread method?

[Andreas Senft]

Just as addition to the solution described by Colin, see this thread. It also contains an example for the application context.

Regards,
Andreas

[Colin Yates]

Just as addition to the solution described by Colin, see this thread. It also contains an example for the application context.

Regards,
Andreas

Hey Andreas! You know what they say, "great minds think alike", but then they also say "fools seldom differ". Not sure which category I fall in

I would suggest that my BeanPostProcessor solution is a little more elegant (and safer) than implementing FactoryBeanAware (or ApplicationContextAware) and InitialisingBean simply because if the bean is a prototype you then setThis will be called with a different instance, which is absolutely what you do not want

I really must blog this...time and all that.

[Andreas Senft]

Hey Andreas! You know what they say, "great minds think alike", but then they also say "fools seldom differ". Not sure which category I fall in

...or I

I would suggest that my BeanPostProcessor solution is a little more elegant (and safer) than implementing FactoryBeanAware (or ApplicationContextAware) and InitialisingBean simply because if the bean is a prototype you then setThis will be called with a different instance, which is absolutely what you do not want

I agree. Only wondering, where I suggested implementing FactoryBeanAware? I guess you refer to my explicit usage of ProxyFactoryBean. In that case, yes, for prototypes it would be a problem.

I really must blog this...time and all that.

Yes, that would really be a good topic.

Regards,
Andreas

[Colin Yates]

I agree. Only wondering, where I suggested implementing FactoryBeanAware? I guess you refer to my explicit usage of ProxyFactoryBean. In that case, yes, for prototypes it would be a problem.

I am not sure who referred to it, someone mentioned (I also mentioned this as well) that if your bean implemented FactoryBeanAware/ApplicationContextAware it could then do a

setApplicationContext(ApplicationContext ctx) { this._decoratedThis = ctx.getBean(getBeanName()) }

etc. but this absolutely ties you down to spring and you need to implement BeanNameAware, ApplicationContextAware and InitialisingBean!