I just committed a couple of little tweaks, one is pretty important,
as it fixes an issue that came up when I fixed the circular reference
over an aop proxy factory. It became impossible to use nonSingleton
aspects. That's now fixed. Also fixed an issue where the
RemoteFactoryBean was broken (Simeon, it should be cool now).
Playing around this weekend brought up another issue, so I think we
need an extra vote or 2. I added the 'BeanFactoryAware' addition as a
DuckType implementation, so if there's a method in a bean
'setBeanFactory' coldspring will supply a reference to the current
bean factory. This can be very handy to preform post creation
processing, if necessary. The big question is, that should probably
search metadata.extends to find the method in any cfc in the
hierarchy, no? Also it seems like we will be doing this for init as
well, because even though I may not agree, you can call init on a cfc
which doesn't have init in it, but extends a cfc that does. It's the
way ColdFusion works, so I guess ColdSpring needs to work that way as
well...
So what to you think about creating a metadata object for
beanDefinitions, and having it search through metadata, so it will
only happen once and find all the flags we will need as we go along
making the bean??
Chris Scott
[EMAIL PROTECTED]
http://cdscott.blogspot.com/
http://www.coldspringframework.org/
