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. > 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 ? -- Tom Chiverton **************************************************** This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at Halliwells LLP, 3 Hardman Square, Spinningfields, Manchester, M3 3EB. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by The Solicitors Regulation Authority. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 2500. For more information about Halliwells LLP visit www.halliwells.com. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [EMAIL PROTECTED] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
