|
From: Rod J. <rod...@in...> - 2003-12-03 12:40:30
|
>Of course, a defined ProxyFactoryBean with a custom FactoryBean as target would proxy the created object, as expected. But as Daniel noted, an auto proxy creator would currently get applied to the FactoryBean instead of the created object. >Should we leave it that way? Bean properties, lifecycle methods, and also bean post processors like ApplicationContextAwareProcessor are in fact meant to be applied on the FactoryBean itself. Could we add a clean option to apply bean post processors to the created objects, if demanded? I think we should leave it that way by default, and perhaps add an alternative option to post process created objects. >BTW, I think that our current PropertyValuesProviderFactoryBean sub-interface is useless. All the bean factory does with the PropertyValues from there is to apply them to the created object via a newly instantiated BeanWrapper: A FactoryBean implementation could easily do that itself with a one-liner, if actually required. Good point. Get rid of it if you like. Regards, Rod |