Blog

Luis Majano

January 18, 2010

Spread the word


Share your thoughts

Welcome to another week of wonderful releases.  We start of with our two awesome logging and mocking frameworks LogBox and MockBox.  They have both just graduated to version 1.1 and can be downloaded today as standalone frameworks or via the 3.0.0 M4 bundle, ahh yes, another blog post after this.

So what's new with LogBox 1.1, well here are the tickets:

890 add all appenders to a logbox category by default even from coldbox apps Fixed
891 category definitions should allow the * for appenders when definining them, instead of listing them Fixed
907 Async Appenders need way to distinguish between threading and not Fixed
910 LogBox standalone is now refactored to work under the logbox namespace Fixed
941 new properties for EmailAppender: useTLS and useSSL Fixed

The most important considerations are that we now have a utility that distinguishes when you are within an executed cfthread in any CFML engine.  LogBox uses this now for all of its asynchronous operations.  We also have refactored the download so LogBox can be installed alongside any ColdBox version or any other framework.  If you want to use LogBox in your ColdBox 3.0.0 applications, you already have it installed, so don't worry. 

Category definitions can now use '*' to define that you want ALL appenders for a specific logging category.  You can also omit them and LogBox will add all of them too.  However, be precise and use '*' if you want all appenders.

The last ticket was contributed to us and it is a great addition to the Email Appender, so now you can set the flags for SSL and TLS a-la-carte.  So enjoy LogBox 1.1!

Now to our mocking and stubbing library MockBox! So what's new with MockBox 1.1:

911 Standalone version should be refactored into its own namespace Fixed
940 new method querySim() to help simulate queries Fixed

We have also refactored the standalone download so it can be used alongside any ColdBox version or framework.  We have also added a nice UDF to simulate queries called querySim().  This way you can easily simulate and mock queries from your tests by doing things like:

mockQuery = querySim("col1, col2
val1 | val2
valrow2 | valRow2
valRow3 | valRow3");

That's it, just use the first line of the call to put your columns comma delimited and then a break and you rows separated by breaks and columns separated by '|'.  A very cool way to simulate queries. 

And finally, it has some minor fixes and tweaks, nothing extraordinary apart from the library itself!

So enjoy these two new standalone releases which can also be found in our upcoming ColdBox 3.0.0 Milestone 4 release!

Add Your Comment

Recent Entries

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

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.

Luis Majano
Luis Majano
March 13, 2026
Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

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...

Cristobal Escobar
Cristobal Escobar
March 13, 2026
Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

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...

Cristobal Escobar
Cristobal Escobar
March 12, 2026