On 6/16/08, Tom Chiverton <[EMAIL PROTECTED]> wrote: > On Monday 16 Jun 2008, Jamie Jackson wrote: > > core framework, there's no clever/clean-ish way to apply my patches > > (via extension/overrides) without modifying framework code, is there? > > > No, I don't think so. > But the core itself is very stable, so maintaining your own patch set > until/unless your changes are accepted and published shouldn't be too hard > (as long as you can access SVN from where you are, you can still get updates, > and update your patches if they conflict). > You'd have to do this anyway, until Reactor made a release version with your > patches in.
Yes, that's how I'm doing things locally. I'm wondering more about programmatic solutions (which probably don't actually exist), but you're right to have pointed out the SVN working copy route. > > I'm guessing it won't be possible unless/until Reactor is re-wired > > with ColdSpring > > > I'm not sure where there could be any benefit to using DI with Reactor, maybe > you could elaborate on your thinking here ? I was jumping off from the following bullet in the (2.0 Alpha) Roadmap (http://reactorframework.com/roadmap): "Make use of ColdSpring in a manner similar to Model-Glue to configure Reactor. Currently many of the core objects in Reactor have dependencies on other objects (in the form of calls to CreateObject). This makes it hard to write meaningful unit tests for these objects. Additionally, it could allow for greater flexibility in configuring the framework." -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [EMAIL PROTECTED] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
