Itb2018 integrating mvc into legacy
3 likes228 views
This document provides guidance on integrating the ColdBox framework into an existing legacy application. It discusses assessing the current application, reasons to migrate to a modern framework like ColdBox, potential gotchas in the migration process, and steps for installing ColdBox and gradually converting the application over time through refactoring and piloting changes on a test system before releasing them. The goal is not to do a full rewrite at once but take a step-by-step approach to refactoring and converting aspects of the application over time to ColdBox.
Itb2018 integrating mvc into legacy
- 1. Integrating MVC into legacy There is hope yet
- 2. The State of Your App â What does your app look like? â Using other frameworks? â Partially converted to Coldbox? â What are your goals?
- 3. Reasons to migrate to a modern framework â Code organization â Devs are all using the same organization and patterns â Consolidated functionality like logging, caching, tier detection â Regular updates â Makes your dev shop more attractive to prospective employees
- 4. Gotchaâs â You still have to write code â Not a silver bullet â Donât try a full 100% rewrite â Baby steps are better than trying everything new at once â Refactor refactor refactor â The pilot system (write a throwaway test)
- 5. Install ColdBox â Environment (tier) detection â Can use legacy checks for environment â Itâs ok for the ColdBox config to reference old application variables â Itâs also possible to find/replace legacy code to use ColdBox settings!
- 6. Application.cfm -> Application.cfc â Watch out for transcendent variables scope â Use onRequest() if needed function onRequest( targetPage ) { variables.mySetting = âmyValueâ; include arguments.targetPage; }
- 7. Add in ColdBox bootstrap â ColdBox is always loaded â onApplicationStart() â You get to decide what requests will be processed by ColdBox â onRequestStart()
- 8. Create a Layout â Convert your main layout â Reuse as much as possible via includes â This will let you start converting views
- 9. Start plugging in ColdBox aspects â Proactively convert legacy: â Logging -> LogBox â Caching -> CacheBox â CFC creation -> Wirebox â This can happen outside of ColdBox!
- 10. Pick a site area to start â Maybe something simple like login â Move .cfm pages into a view â Implicit view dispatch â Swap out build links calls
- 11. Handle external URLs â Just change them and have people update bookmarks â Put in URL rewrites at the web server level â Put in routing in your Application.cfc to re-route to ColdBox
- 12. Shorten your feedback loop â When you have a part of the app working, test it and RELEASE IT! â Donât try to save up and do a huge chunk. Youâll never finish! â Use this as an opportunity to do script conversion, etc but donât get bogged down â Employ group code reviews to discuss conventions and stay on the same page â Make sure you update your product owner so they know about your progress!
- 13. Legacy/ColdBox App Demo â https://github.com/bdw429s/coldbox-legacy-app-demo â Clone repo and start server â Each page tells you how it works â Half of the demo site runs legacy .cfm files â Half of the demo site runs ColdBox handlers