On Mon, Sep 1, 2008 at 6:35 AM, Tom Chiverton wrote: ... > I changed our Reactor core files to make the _getConfig() available, and it's > more trouble than it's worth, so went back and did it 'the right way': > <bean id="reactorConfiguration" class="reactor.config.Config"> > <constructor-arg name="pathToConfigXml"> > <value>/reactor.xml</value> > </constructor-arg> > </bean> > <bean id="reactor" class="reactor.reactorFactory"> > <constructor-arg name="configuration"> > <ref bean="reactorConfiguration" /> > </constructor-arg> > </bean> > > The reactorConfiguration bean is then available for your application to use.
??? I'm not sure what you mean. Why is it more trouble, and what were you using it for? It's been working fine for me. *shrug* =] I did it because I have something that uses Hibernate, and I liked how you can get the "current" configuration from Hibernate, *from* hibernate, vs another object. What are you going to do with one or the other, alone? *scratches head* :] I'm sure it's there, but I'm just missing the "badness" of having access to the current config from the factory. If only for introspection type stuff. -- We are selfish when we are exclusively or predominantly concerned with the good for ourselves. We are altruistic when we are exclusively or predominantly concerned with the good of others. Mortimer Adler -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [EMAIL PROTECTED] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
