Blog

LogBox 1.6 Released!

Luis Majano January 17, 2011

Spread the word

Luis Majano

January 17, 2011

Spread the word


Share your thoughts

Our amazing LogBox: Enterprise Logging Library reaches another step in awesomeness to version 1.6.  This release includes incredible performance tuning, fixes and some cool new updates:

This release includes the following:
  • coldbox-1128  Convenience methods for log checking: canDebug(), canInfo(), canWarn(), canFatal(), canError().

  • coldbox-1129 Better documentation on logging classes and levels

  • coldbox-1139 Enhance the logEvent class to have a better serialization schema for extraInfo, it can use convention $toString() on the incoming extra info object to do auto serialization on it.  If not, if complex it will use JSON notation.

  • coldbox-1147 LogBox category parsing needs a length check when the category sent is blank

  • coldbox-1154 performance tuning that is outta hand!
So to use the new $toString() convention, all you need to do is create a function called "$toString()" that returns a string representation of the object it exists on.  Once this object is sent for logging via the extraInfo argument (2 argument in any log operation), LogBox will call this serializer for you.

function $toString(){
  return "I am a string representation of this CFC";
}

We also want to leave you with a performance tip when using LogBox.  Don't send log methods without checking first if you can actually send something to its logging level.  This will help tremendously when generating log messages and accelerate your application.  So for example:

Don't do this:
log.warn("This is a warning");

Do this:
if( log.canWarn() ){
   log.warn("This is a warning");
}


So what are you waiting for, download it now!

Add Your Comment

Recent Entries

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026