Blog

ColdBox 4.0 Module Enhancements

Curt Gratz February 02, 2015

Spread the word

Curt Gratz

February 02, 2015

Spread the word


Share your thoughts

One of the biggest things we changed about ColdBox 4.0 is making tons of the core completely modular.  To support this change, we needed to enhance our modules architecture which brought some cool new features to you.  

Module Inception

Every time I talk about ColdBox modules with people, I get asked if modules can contain modules, which up to now wasn't an option. But the first Module Enhancement I'd like to bring to your attention is just that.  We call it Module Inception.  This will allow for even greater ways for you to build and architect your applications.  Modules can be nested to the Nth degree.  Creating a ton of options and flexibility for you the developer in how you organize your code.

Module Dependencies

The next Module Enhancement I'd like to point out is Module Dependencies.  This allows for you to ensure the modules that are needed to support your module are available and active before before your module is loaded.  This is handy in controlling activation order (avoiding chicken and egg problems) and again gives you better options as you architect your applications with modules.

Module Model Wirebox Mappings.

Now your module models will be mapped in Wirebox automatically similar to how your ColdBox model folder is mapped.  The mappings will be setup with the DSL that is model@modulename.  For example.

property name="orderService" inject="OrderService@store";

Of course, if you don't want it to work this way, we give you a setting called autoMapModules that you can set to false if you don't want to map your models in your modules.

These are just a few of the Module Enhancements.  To check them all out, read our wiki page at 

http://wiki.coldbox.org/wiki/WhatsNew:4.0.0.cfm#Module_Enhancements

Add Your Comment

Recent Entries

BoxLang 1.17 Series Part 3 : Encrypted Config Secrets

BoxLang 1.17 Series Part 3 : Encrypted Config Secrets

Everyone knows the datasource password should not be sitting in plain text in a config file. Everyone has also, at some point, shipped exactly that, because the alternative was a pile of environment variable plumbing that nobody wanted to build on a deadline. x

Luis Majano
Luis Majano
September 08, 2026
BoxLang AI 3.4 Blog Series Part 3 : Batched Approvals

BoxLang AI 3.4 Blog Series Part 3 : Batched Approvals

Here's a bug that's easy to miss until it bites someone in production: an agent turn asks for two tool calls at once, both need human approval, and only the first one actually suspends. The second one gets silently skipped. Not rejected, not queued, just gone. That's what happened before 3.4.0, and it's fixed now with batched tool-call approvals.

Luis Majano
Luis Majano
September 08, 2026
Getting Started with BoxLang as an Alternative CFML Engine

Getting Started with BoxLang as an Alternative CFML Engine

If you have an existing ColdFusion or Lucee application, one of the first questions you may have about BoxLang is probably not:

“Should I rewrite my application in BoxLang?”

It is much simpler:

“Can BoxLang run the CFML application I already have?”

That was the focus of veteran CFML troubleshooter Charlie Arehart’s session at Into the Box 2026, Getting Started with BoxLang as an Alternative CFML Engine.

Cristobal Escobar
Cristobal Escobar
September 08, 2026