ColdBox 4.0: What We Kept

CacheBox, ColdBox MVC, LogBox, Tutorials, WireBox

Nathaniel Francis February 20, 2015

Spread the word

Nathaniel Francis

February 20, 2015

Spread the word

Share your thoughts

State of the ColdBox

ColdBox 4.0 is a major release. The most significant major release since it went alpha/1.0 in June of 2006.

Most of the changes have been focused around streamlining, efficiency, extendability, and leaning out those things aren't really essential.

This may leave you wondering, "What's left?"

Helping the core

Outside of the absolute core, essential code that makes ColdBox tick; three of the iconic Box products are "baked in" to the core.

WireBox 2.0
CacheBox 2.0
LogBox 2.0

Each of these libraries are automatically in ColdBox 4.0 because we use them to do ColdBox magic - they are an essential part of ColdBox processes.

Everybody gets an update!

As part of the ColdBox 4.0 release, each of these libraries also got their own major updates.

Wirebox 2.0 got some new functions and features
LogBox 2.0 deprecated its xml support and had some bug fixes
CacheBox 2.0 also deprecated its xml support

Not just for ColdBox

Each of these libraries are also available for non-ColdBox CFML use. We find them so useful that we don't want to keep them to ourselves. Each of them is available on ForgeBox for download and use in any CFML application.

To make working with these libraries easy, whether you are working in ColdBox or separately, each library has their own refcard to help make things simple and clear.

BoxLang 1.17 Series Part1 : Module Inception

BoxLang has always been an extensible language. As of 1.17.0, it is a hierarchically extensible one. Every module ecosystem you have worked in is flat. You declare a list of dependencies and something outside the language, a package manager or a build tool, resolves and downloads and orders them. The language itself has no opinion about the shape of the graph. It sees a list, not a tree.

Why Migrate from ColdFusion to BoxLang? 10 Reasons to Modernize Your CFML Applications

For organizations running applications built with ColdFusion or CFML, modernization often comes with an uncomfortable question:

“Do we keep investing in the platform we already have, or do we rewrite everything in another language?”

That choice is not as binary as it may seem.

At Into the Box 2026, Ortus Solutions Senior Architect and BoxLang core developer Jon Clausen presented a session titled “Top Ten Reasons to Migrate to Bo...

Blog