Blog

LogBox 1.2 Released!

Luis Majano March 19, 2010

Spread the word

Luis Majano

March 19, 2010

Spread the word


Share your thoughts

On the spirit of non-stop releases, here is LogBox version 1.2.  Apart from some bug fixes we have squeezed in some great new functionality, especially when dealing with configuring LogBox and portability. Check out our milestone tickets for further review. Version 1.2 Tickets
  • Added some new methods to the LogBoxConfig object: resetAppenders(), resetCategories and resetRoot() to reset some configurations.
  • Fixes on appender declarations and layouts
  • Addition of the LogBox DSL to coldbox configuration file, so now you can configure logbox via a cool DSL
  • Ability to configure LogBox via a simple CFC with a simple configure() method and our cool DSL
The major portion of this release is three words "Portabiity in Style".  We wanted to add a new way to configure LogBox in ColdBox style, a cool data definition DSL. Of course, our documentation is updated and now online: http://wiki.coldbox.org/wiki/LogBox.cfm#LogBox_DSL. Here is a little tast of the DSL: function configure(){ logBox = { // Appenders appenders = { appenderName = { class="class.to.appender", layout="class.to.layout", properties={ name = value, prop2 = value 2 } }, // Root Logger root = {levelMin="FATAL", levelMax="DEBUG", appenders="*"}, // Granualr Categories categories = { "coldbox.system" = { levelMin="FATAL", levelMax="INFO", appenders="*"}, "model.security" = { levelMax="DEBUG", appenders="console,twitter"} } // Implicit categories debug = ["coldbox.system.interceptors"], info = ["model.class", "model2.class2"], warn = ["model.class", "model2.class2"], error = ["model.class", "model2.class2"], fatal = ["model.class", "model2.class2"], off = ["model.class", "model2.class2"] }; }

Add Your Comment

Recent Entries

Inherited a CFML Application With Few Tests? Here’s Where to Start!

Inherited a CFML Application With Few Tests? Here’s Where to Start!

You need to change an application that has been running for years.

It might be a ColdFusion customer portal, a Lucee application supporting internal operations, or a CFML system your team is preparing to modernize. People depend on it, but some of its behavior lives in old tickets, scattered documentation, and the memory of whoever has supported it longest.

Now a release is approaching. You know more testing would help. The difficult part is deciding where to begin without putting every other priority on hold.

Start with one important workflow and build evidence around what it needs to do.

Explore Ortus Quality Assurance Services

Maria Jose Herrera
Maria Jose Herrera
October 27, 2026
Your ColdFusion Upgrade Passed. Did Your Business Workflows?

Your ColdFusion Upgrade Passed. Did Your Business Workflows?

The server restarted. The administrator shows the expected version. Your homepage loads, and a few familiar screens look fine.

Would you tell the business the upgrade is complete?

Consider an illustrative scenario: a customer submits an order after an upgrade. The application saves it and displays a confirmation page. But the confirmation email never arrives, and the scheduled process that sends the order to fulfillment has not completed.

From the browser, the transaction...

Maria Jose Herrera
Maria Jose Herrera
October 22, 2026