[coldspring-dev] Hi Everyone!

Thu, 04 Jan 2007 20:49:28 -0800

OK, there's no reason why ColdSpring shouldn't take care of it's own business, soooo. 

I have tweaked the ProxyFactoryBean to make sure that the BeanFactory is in the location it is expected (this will be the default location in app scope, unless you specify a beanFactoryName as a property of ProxyFactoryBean). This actually can be pretty handy if you do not know how the BF is being instantiated, such as in the case of MG. But, since you may have other uses for locating the BF, outside of remoting, I also added a BeanFactoryPostProcessor for locating the BF. Sounds confusing, but basically, if you define this new bean in the factory (BeanFactoryLocator, suggest a better name...), when the factory loads, it will automatically create a reference to the BF in app scope in either the default location or a name specified in the  beanFactoryName property.

Sorry I have not yet committed this, I need to check it, and it's 11:45, and I have a glass of Nobb Creek sitting next to me... I'll run  it through some tests and commit tomorrow!

Chris


On Jan 4, 2007, at 11:03 PM, Chris Scott wrote:

Wow, this one seems to have slipped, and I am sorry there. I looked through the MG issue tracker and I think maybe we should bring this back up and look for a clean solution. Basically, MG needs to have an option to use ColdSprings locator class, BeanFactoryUtils to store the CS factory. This can use either a default key, or a named one, which is easy to pass on to your remote proxies in their configuration. Let me try to get Joe again, because I really think that MG should have the same level of support for CS as MachII does.]

I am thinking now... Maybe I can just work up a quick BeanFactoryAware bean that will place CS in app scope for you... Perhaps a BeanFactoryPostProcessor...

On Jan 4, 2007, at 6:06 PM, Derek Perez wrote:

http://www.mail-archive.com/[email protected]/msg00285.html


Reply via email to