Hey, where'd my debugger go?

ColdBox MVC, CommandBox, Modules, Tutorials, WireBox

Curt Gratz February 09, 2015

Spread the word

Curt Gratz

February 09, 2015

Spread the word

Share your thoughts

You may be wondering where all that amazing debugging information went in your ColdBox 4.0 application. Have no fear. You can still have your cake and eat it too. We modularized it (sensing a theme in ColdBox 4.0 yet?) So, how do you get all that wonderful debugging info?

Easy! Using CommandBox, run the following command.

box install cbdebugger --saveDev

Notice the --saveDev we added to our command. This is handy as it tells CommandBox that you only want this as a dependency for your application in development.

Once the debugger module is installed, you can control the settings via the debugger structure in your main Coldbox config file.

Also, if you need access to the debugger service or the timer, they are available via the following WireBox mappings.

debuggerService@cbdebugger
timer@cbdebugger

Just call getInstance() on either to snag them as needed.

Debug to your heart's content.

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Spring Boot developers know the pain of evaluating view technologies. Thymeleaf is great — until you need more expressiveness. FreeMarker is powerful — until the syntax fights you. What if you could write templates in a dynamic JVM language that gives you the full power of the platform, feels natural, and requires zero setup to integrate?

Meet the BoxLang Spring Boot Starter.

Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

The growing need to evolve legacy financial platforms safely

Many Swiss banks and financial institutions still operate important systems built on ColdFusion and CFML platforms.

These systems manage a wide range of functions, including:

internal banking workflows
reporting systems
client portals
data integration platforms
compliance and risk management tools

In many cases, thes...

Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Many ColdFusion environments operate in a reactive mode without realizing it.

Everything seems fine… until something breaks.

A server crashes.

Performance drops suddenly.

An integration stops working.

A security audit reveals missing patches.

At that point the response is urgent:

“Can someone help us fix this now?”

Emergency support is sometimes unavoidable. But when reactive intervention becomes the norm, it usually means something deep...

Add Your Comment

Comments (2)

Feb 11, 2015 18:16:55 UTC

by Jim Priest

If you are like me and just getting started with ColdBox - once you have installed the debugger module, look under /modules/cbdebugger/readme.md and there is an example 'Debugger Settings' of what you need to copy to your ColdBox config file to enable things.

Feb 27, 2015 00:03:15 UTC

by Dan O'Keefe

I get command cannot be resolved. Isn't it supposed to just be install cbdebugger --saveDev?

Blog