A betters solution than just deproxying half the dependancy. I tried digging through constructBean to figure out what's the matter, but quickly had my brain turned into mush. It seems like having the ProxyFactoryBean in there shouldn't matter because it's still a singleton; just a matter of chaining the getObject() call after it. But there's a pile of "factories are special" comment and conditionals in constructBean, so I'm clearly not aware of why it matters (duh).
cheers, barneyb On 10/20/06, Chris Scott <[EMAIL PROTECTED]> wrote:
Hmmmmmm. And also, Grrrrrr. Circular dependencies are the monsters that keep me up at night and their friends factories make crushing them a bloody battle. I'll have to take a good look at what's happening here and see what we can do. BeanFactoryAware and setup methods can also relieve circular dependencies, as using a setup method to complete the initialization of your components can give you a way to stagger your object creation. Helps ColdSpring along... Chris Scott [EMAIL PROTECTED] http://cdscott.blogspot.com/ http://www.coldspringframework.org/
-- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites.
