inheritance vs. non-inheritance Applicaiton.cfm

The Coldbox distribution application templates include both inheritance and non-inheritance versions of Application.cfm. Prior to 3.7.0, the inheritance version was the default. The “What’s New With ColdBox 3.7.0” document includes the following:

Improvements
[COLDBOX-167] - Make non-inheritance approach the default for application templates

Major Enhancements-Improvements
Make non-inhertance approach the default for application templates

I switched to the non-inheritance version long ago but, frankly, can’t remember why. What are the pros and cons to each? What was the reason for making the switch in the distribution?

Thanks
Bob

I’m not sure why Luis switched the default, but the reason I typically use the non-inheritance approach is if I want to use app mappings. Application-specific mappings are configured inside of Application.cfc which means the mapping doesn’t exist in time to resolve the extends attribute of the Component itself.

Thanks!

~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

Brad,

I use mappings so that must be why I switched. Thanks for the reply.

Bob