It was on my blog. Joe wrote this. I've only used it once myself.... for the most part it seems like it's not a great idea to use this, but I can see cases where it might be really useful.
Here's an example. Let's say you've configured the reactorFactory using coldspring. When you ask the bean factory for the reactorFactory the bean factory will look to see if the object has a setBeanFactory method that accepts an object of type coldspring.beans.beanFactory. Because the reactorFactory does, in fact, have such a method the CS bean factory will pass itself in when constructing the object. The ReactorFactory's init method passes the beanFactory into the ObjectFactory which, in turn, passes the beanFactory to Reactor generated objects it instantiates. These objects all have a method, _getBean, which you can use to get at coldspring configured beans via the beanFactory. This means, for example, that you could have objects in your model accessible from Reactor records. I'm having a hard time coming up with where this might be useful though. I've only used this feature one time on a new version of my blog I'm writing. This was to get the blogConfig to se how many days worth of entries I should return. I've been planning on removing this usage anyhow. It's my personal opinion that Reactor objects should be used exclusively for data operations and calculations. They shouldn't get too mixed up in your "real" model. That is to say that Reactor objects aren't your model. Thus, the usage of this is debatable. Joe said something about a current debate about anemic domain models. I'm not up to speed on this so I can't speak to it. Anyhow, it's there if needed. Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield Sent: Tuesday, October 10, 2006 10:32 AM To: [email protected] Subject: Re: [Reactor for CF] BeanFactory Perhaps if you provide a link to where you read this, we can comment on it? The way you describe it does indeed sound backward... On 10/10/06, Tom Chiverton <[EMAIL PROTECTED]> wrote: > Just read that Reactor lets you access ColdSpring configured beans. > Isn't that backward ? ColdSpring should (and does) provide access to Reactor > for the beans it manages, rather than the database abstraction layer > (Reactor) managing the beans that depend on it. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
