Blog

Brad Wood

November 13, 2020

Spread the word


Share your thoughts

Adobe released ColdFusion 2021 this week.  It's a pretty big release with a modularization of the core engine and a nice list of language enhancements. 

https://helpx.adobe.com/coldfusion/user-guide.html/coldfusion/cfml-reference/new-changed-functions-coldfusion-2021.ug.html

Here's what you need to know for using it with CommandBox.

ForgeBox

The 2021.0.0 version is already on ForgeBox.  If you're thinking, "Hey, wasn't this version 2020?" you'd be right.  It got...changed at some point recently.  You can start an ACF 2021 server just like any other Adobe server right now like this:

CommandBox> server start cfengine=adobe@2021

We've only done basic testing, but the server seems to start up just fine.  Check the server log, or do a --debug start if you have any issues.

server log
server start --debug

CFConfig

If  you're using CFConfig, you'll need to update it to the latest version so it recognizes the version. 

CommandBox> update --system

We haven't added any new settings to CFConfig yet, so it you find some new 2021 settings you need to be able to import/export please let us know what they are.

Modular Architecture

Following in the footsteps of Lucee 5, ACF 2021 uses OSGI bundles to load/unload additional functionality into the server.  This makes the core engine a lot smaller, but it also means your app may not compile until you've added in some missing pieces.  Unlike the default Lucee server that ships with most extensions, Adobe CF 2021 ships with almost no extensions.  We're still discussing how to handle this  in ForgeBox. 

For Lucee, I have two ForgeBox slugs: lucee and lucee-light.  The former coming with most extensions and the latter coming with none.  We've considered adding additional options to download an Adobe engine with all the same functionality that previous versions had.  However, I'm not sure if time is better spent putting effort into making it easy to declare your needed packages and just let CommandBox automatically install those packages for you.  

cfpm

The ColdFusion Package Manager, or cfpm is a tool that ships with ACF 2021 in the form of a script in the cfusion/bin folder you can run to download and install additional functionality into your server.  Unlike Lucee, ACF 2021 doesn't appear to have any file system based convention whereby you can download these packages manually, place them in a special deploy folder, and have the engine just slurp them in.  It seems the installation needs to flow through the cfpm script.

You can run cfpm from inside CommandBox like this.  It works well, but it's not pretty.

!C:/Users/Brad.development/Documents/GitHub/cfconfig/tests/resources/adobe2021/serverHome/WEB-INF/cfusion/bin/cfpm.bat install feed

As such, I've added a new feature to the latest CommandBox 5.2.0-RC.1 build to make it easier for you to call the cfpm tool without needing to dig into the bowels of your server installation to find it.  CommandBox now has a top level command called "cfpm"  that, when run in the webroot of an Adobe 2021 server, will find the location of the cfpm.bat or cfpm.sh script and execute it, passing along any parameters you supply

// This opens the cfpm shell.  Type "q" and hit enter to exit back to CommandBox
CommandBox> cfpm

// This directly runs a cfpm command
CommandBox> cfpm install feed

This should make life a little easier while we work on a better convention for CommandBox to "auto-install" packages from your box.json or server.json file on server start.

Remember, you need to update to the CommandBox 5.2.0 build to get this feature.

Issues

If your a ColdBox or TestBox user, you may run into issues.  ColdBox 6's app templates don't appear to run at all on CF 2021 and we've heard reports of TestBox not working as well.

https://tracker.adobe.com/#/view/CF-4210899

https://tracker.adobe.com/#/view/CF-4210912

Add Your Comment

Recent Entries

12 Days of BoxLang - Day 4: TestBox

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Victor Campos
Victor Campos
December 11, 2025