Download as PDF, PPTX
![MODULECONFIG.CFC PROPERTIES
// Module Properties
this.title = "cbswagger";
this.author = "Jon Clausen <jon_clausen@silowebworks.com>";
this.webURL = "https://github.com/coldbox-modules/cbSwagger";
this.description = "Swagger API documentation from your routes";
this.version = "@build.version@+@build.number@";
// If true, looks for views in the parent first, if not found, then in the
module. Else vice-versa
this.viewParentLookup = true;
// If true, looks for layouts in the parent first, if not found, then in module.
Else vice-versa
this.layoutParentLookup = true;
// Module Entry Point
this.entryPoint = "cbswagger";
// Model Namespace
this.modelNamespace = "cbswagger";
// CF Mapping
this.cfmapping = "cbswagger";
// Module Dependencies That Must Be Loaded First, use internal names or aliases
this.dependencies = [ "swagger-sdk" ];](https://image.slidesharecdn.com/coldboxhierarchicalmvc-171120162539/75/ColdBox-Hierarchical-MVC-for-ColdFusion-CFML-33-2048.jpg)
![MODULECONFIG.CFCCONFIGURE
function configure(){
settings = {
caching = false,
mailTo = "lmajano@ortussolutions.com"
};
layoutSettings = { defaultLayout = "relax.cfm" };
i18n = {
resourceBundles = {
"cbcore" = "#moduleMapping#/i18n/cbcore"
},
defaultLocale = "en_US",
localeStorage = "cookie"
};
interceptorSettings = {
// ContentBox Custom Events
customInterceptionPoints = arrayToList( [
// Code Rendering
"cb_onContentRendering", "cb_onContentStoreRendering"
] )
};
routes = [
//Module Root Requests
{ pattern=“/", handler="Main", action="index" },
// Convention Route
{ pattern=":handler/:action?" }
];
}](https://image.slidesharecdn.com/coldboxhierarchicalmvc-171120162539/75/ColdBox-Hierarchical-MVC-for-ColdFusion-CFML-35-2048.jpg)
Uploaded byOrtus Solutions, Corp
ColdBox Hierarchical MVC for ColdFusion/CFML
The document discusses the modernization of legacy monolithic CFML applications through the adoption of HMVC architecture and microservices. It highlights the benefits of modularization, improved organization, testability, and the use of ColdBox modules to facilitate development. Additionally, it explains the importance of adhering to MVC practices and the need for a paradigm shift to meet evolving software complexities.
More Related Content
Similar to ColdBox Hierarchical MVC for ColdFusion/CFML
![Brad wood - Integrating MVC Into Legacy [Into The Box 2020]](https://cdn.slidesharecdn.com/ss_thumbnails/bradwood-integratingmvcintolegacy-200508221848-thumbnail.jpg?width=640&height=640&fit=bounds)
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
ColdBox Hierarchical MVC for ColdFusion/CFML
- 1. Hierarchical MVC Transform yourMonolith
- 2. WHO AM I? •Luis Majano - Computer Engineer • Imported from El Salvador • Houston,Texas • CEO of Ortus Solutions • Creator of many boxes www.ortussolutions.com @ortussolutions @lmajano
- 3. AGENDA • The LegacyProblem • Monolithic Applications • HMVC Architecture • ColdBox Modules • API Demo
- 4. “Software is alwaysbound to change”
- 5.
- 6. LEGACY PROBLEM • GivesCFML a bad name • Security Issues • Performance Issues • Employee Issues • Development Issues • Finding Developer Issues
- 7. LEGACY PROBLEM •>35% NoMVC •>60% No DI •>55% No Testing FuseBox is NOT MVC
- 8. LIKE MY CFMLAPP? • MVC Framework or spaghetti hell? • OO or cfinclude hell? • Automated Tests? Continuous Integration? • Agile/Scrum Methodologies? • Source Control? (Zip files don’t count!) • Continuous Delivery? Container Strategy? • Developer Automation?
- 9.
- 10. HOW DO WEMODERNIZE CFML?
- 11. BACK TO THESCHOOL OF ARCHITECTURE
- 12. 1. COHESION -COUPLING
- 13. 2. MVC • Separateslayers of concerns • Helps enforce OO • Specialized team members • but • Layers are still tightly coupled • MVC Monoliths
- 14. 3. N-TIER -MEXICAN CHALUPA • Add more layers for organization • Layers are still tightly coupled • Still monolithic!
- 15.
- 16. 4. HMVC • Evolutionof MVC • No more lasagna • Independent MVCTriads • Benefits • Higher Cohesion • Lower Coupling • Modularization • Better Organization • Reusability • Extensibility • Testability
- 17. 5. MICROSERVICES AN APPROACHTO DEVELOPING A SINGLE APPLICATION AS A SUITE OF SMALL SERVICES, EACH RUNNING IN ITS OWN PROCESS AND COMMUNICATING WITH LIGHTWEIGHT MECHANISMS. Martin Fowler
- 18. 5. MICROSERVICES M C V MC V M C V
- 19. • Legacy codeupdates less intimidating • Fault tolerance • Versionable & Maintainable • Short release cycles • Monoliths Evolution 5. MICROSERVICES Identify Break Out Scale
- 20. COMMANDBOX-DOCKER Run any CFMLEngine Run any WAR Portable Server Settings Portable CFML Engine Settings Image Healthchecks Secure Headless Modes
- 21.
- 22. A FUNDAMENTAL CHANGE IN APPROACH OR UNDERLYING ASSUMPTIONS. PARADIGMSHIFT: MODERNIZE…
- 23. Monolithic) App) App#Security# Billing# Blog# Cart# User# Admin# EVOLVETO HMVC MODULARITY “Asa system evolves, It’s complexity will increase unless work is done to maintain or reduce it.” Lehman’s 2nd Law of software evolution
- 24. WHAT IS AMODULE? "In structured design and data-driven design, a module is a generic term used to describe a named and addressable group of program statements” by Craig Borysowich (ChiefTechnologyTactician) “A software module is a deployable, manageable, natively reusable, composable, unit of software that provides a concise interface to consumers.” by Kirk Knoernschild
- 25. COLDBOX MODULES =SUPER POWERS • Mini MVC applications • Addressable • Composed • Dependencies • Runtime Installed • Reloaded • Unloaded
- 26. COLDBOX MODULES AREOLD Available since v3.0.0 (2011)
- 27.
- 28. WHAT DOYOU GET? •MVC Conventions • Automatic Model Mappings (DI) • Automatic CFML Mappings • Automatic URL Routing • Automatic Interceptors • Overridable Settings • Environment Detection • Module Dependencies
- 29.
- 30. Anatomy of aModule ModuleConfig.cfc handlers layouts models modules modules_app Module Name (unique on disk) box.json views
- 31.
- 32. MODULECONFIG.CFC • Simple CFC •Bootstraps your module • Must exist in the root of your module folder • Has public properties • Callback methods • Tier-detection enabled • It’s an interceptor too!
- 33. MODULECONFIG.CFC PROPERTIES // ModuleProperties this.title = "cbswagger"; this.author = "Jon Clausen <jon_clausen@silowebworks.com>"; this.webURL = "https://github.com/coldbox-modules/cbSwagger"; this.description = "Swagger API documentation from your routes"; this.version = "@build.version@+@build.number@"; // If true, looks for views in the parent first, if not found, then in the module. Else vice-versa this.viewParentLookup = true; // If true, looks for layouts in the parent first, if not found, then in module. Else vice-versa this.layoutParentLookup = true; // Module Entry Point this.entryPoint = "cbswagger"; // Model Namespace this.modelNamespace = "cbswagger"; // CF Mapping this.cfmapping = "cbswagger"; // Module Dependencies That Must Be Loaded First, use internal names or aliases this.dependencies = [ "swagger-sdk" ];
- 34.
- 35. MODULECONFIG.CFCCONFIGURE function configure(){ settings ={ caching = false, mailTo = "lmajano@ortussolutions.com" }; layoutSettings = { defaultLayout = "relax.cfm" }; i18n = { resourceBundles = { "cbcore" = "#moduleMapping#/i18n/cbcore" }, defaultLocale = "en_US", localeStorage = "cookie" }; interceptorSettings = { // ContentBox Custom Events customInterceptionPoints = arrayToList( [ // Code Rendering "cb_onContentRendering", "cb_onContentStoreRendering" ] ) }; routes = [ //Module Root Requests { pattern=“/", handler="Main", action="index" }, // Convention Route { pattern=":handler/:action?" } ]; }
- 36. Bonus: ModuleConfig is alsoan interceptor box install cors
- 37. LEVERAGING WIREBOX • Automaticallymaps all your models to • {modelName}@{moduleName} • property name=“builder” inject=“builder@qb”;
- 38.
- 39.
- 40.