On 4/20/06, Chris Scott <[EMAIL PROTECTED]> wrote: > reason we decide aspects are dependent on the proxied beans that they > also need to be inserted into (Sean!).
It's a perfectly reasonable use case, honestly it is. > A: add an attribute 'beanFactoryAware' to the xml file for the bean > (Which is NOT in the Spring DTD, I don't like it) Ugh! :( > B: add an attribute to the <cfcomponent> tag: <cfcomponent > name="myBFAComponent" coldSpingBeanFactoryAware="true" ... /> Ugh! :( > C: have ColdSpring just assume that since you have the method > setBeanFactory() in your component, what you mean is that this is > a BeanFactoryAware bean. This seems like the most idiomatic ColdFusion approach since it is a dynamically typed language. And it just means you cannot have a bean id="beanFactory" (which I don't think you should anyway - it's too generic a name and besides, that's what ColdSpring is already). However, I'm not sure how any of that helps my use case - what would I have to change in my bean definition file (ggcc10) in order to use this and avoid the circular aspect dependency? -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
