Blog

ColdBox 3.0.0 Beta 3 Released!

Luis Majano November 13, 2009

Spread the word

Luis Majano

November 13, 2009

Spread the word


Share your thoughts

In spirit of releasing more stuff, here is our next milestone for our 3.0.0 release Beta 3.  This beta keeps in spirit of innovation of the 3.0.0 series, but please note that if you are upgrading from previous releases you will need to follow our compatibility guide in order to get your application 3.0.0 compatible.  You can check out our What's New in 3.0.0 document and see all of the documentation of the new features or changed features of 3.0.0.  Please mark it as the documents are constantly being updated as release progresses.  We are still in transition in terms of documentation, tickets and all, so we will soon have all our docs migrated to our new wiki.  However, we will continue to update the original wiki documentation until our migration is complete.  Tickets are a little tricky since we are not touching our databases until the assembla move is complete and I am still waiting on their imports.

This is our current beta 3 tickets: http://ortus.svnrepository.com/coldbox/trac.cgi/query?group=status&milestone=3.0.0-Beta3 but more have been completed and an update on this will be done once our migration is complete.

Some enhancements not yet ticketed:
  • Ability to now return simple data from event handlers in MVC mode and they will be rendered on the screen.  This gives in the ability to create reusable rendering events or viewelets by just rendering events: #runEvent('viewlet.X')#.  This also encapsulates the viewlet call and can even make the viewlet be rendered via Ajax or in a portlet. (ColdBricks anyone!)
  • New XML Application loader that will load ColdBox applications that are configured via XML.
  • Preliminary CFC Application loader that will have the ability to load ColdBox applications with no more XML (YEEEEHAAA!!), full CFC goodness! (Not yet functional)
  • The ColdBox cache is now know as "cboxCache" and has a new configuration element: EvictCount which defaults to 1.  This means that when the cache evicts objects from the cache due to limits or thresholds it can evict a count that you set.
  • The MailService plugin is now fully functional for Railo, Open BD and CF.
  • The ColdBoxExtensionsLocation is now a setting that can be configured in your application file.  This setting points to a folder where you can drop plugins and internal ColdBox services.  These plugins will now either override CORE coldbox plugins or be available via "getPlugin()" calls.  The services are not yet operational but will give you the ability to extend the core framework via internal coldbox services which include even an internal coldbox event model.
  • The majority of plugins and interceptors have been updated to leverage LogBox for logging capabilities and can be configured via the ColdBox configuration file.
  • Includes LogBox 1.0
  • Includes MockBox 1.0
  • Overall stability and performance improvements.  Our load tests indicate a startup improvement of 15-20% and a overall request improvement of 15%.
  • Stay tuned as ColdBox 3.0.0 continues with its milestones.  Expect another milestone release by the end of the year!

Here are some ticketed items:
  • #748
  • SES can now be configured to use logbox debugging using its class category
  • #866
  • Refactor Utilities plugin into more granular existing plugins. This will need a compatibility check as some methods will be moved to their accompanying utility objects.
  • #872
  • New annotations for Integration Testing components: appMapping, configMapping, coldboxAppKey, loadColdbox
  • #878
  • new setting for coldbox extensions location: ColdBoxExtensionsLocation
  • #879
  • update bean factory metadata parsing to accept cfproperty with no type defined so it defaults to the default DSL marker
  • #881
  • addAsset() is now XHTML compliant
  • #882
  • flash RAM not keeping objects for web flows, but now it does
  • #883
  • expirations and clearing are note affecting metadata on cached elements.
  • #886
  • ses convention name value pairs not setting blank values for the first convention name value pair only
  • #887
  • remove purgeView() calls, they don't make sense anymore as all this is done via the cachemanager
  • #889
  • antisamy update to use appendPaths() instead of setting itself up.
  • #892
  • environment control not loading per environment interceptors
  • #893
  • review FORM/URL testing on unit testing cases, resolved
  • #894
  • wrong path for the MockController in the base test case, wrong path is TestController
  • #896
  • fix for boolean values not coming out as true or false in JSON conversions
  • #897
  • new interception point: preProxyResults that will execute before the coldbox remote proxy returns results to a caller via the process() method.
  • #899
  • new plugin anotation: autoInit = [boolean=true] so you can disable auto calling of the constructor
  • #900
  • new renderData() arguments for setting header info: statusCode, statusText
  • #901
  • cf9 serialization/deserialization issues when dealing with object serializations, not converting to/from binary



Add Your Comment

Recent Entries

Coming Soon:  Version 4 Docker CommandBox Images with Enhanced Performance

Coming Soon: Version 4 Docker CommandBox Images with Enhanced Performance

CommandBox Docker images were the first CFML docker images and have nearly 2 million pulls, since their inception, to date. It's been a source of pride at Ortus that these images have been the most popular and reliable way to run CFML in containers and we are so very pleased to announce the next evolution, which will be the v4 images which run entirely on the BoxLang CLI and represent a significant overhaul of the image architecture.

These images are now available to test by appending -snapshot to your existing version tags and wil be released as stable, once CommandBox v6 emerges from release candidate status and is published as stable.

Jon Clausen
Jon Clausen
October 30, 2026
Free observability with BxMCP: give your AI agents eyes inside a live BoxLang runtime

Free observability with BxMCP: give your AI agents eyes inside a live BoxLang runtime

Ortus Solutions today announces that bx-mcp, the Model Context Protocol (MCP) server for BoxLang, is now free for everyone. Install it, point any MCP capable client at it, and your AI coding assistant, IDE agent or automation pipeline can inspect and operate a live BoxLang runtime: JVM, caches, datasources, slow requests, schedulers, logs and more. No BoxLang+ subscription required.

Luis Majano
Luis Majano
October 29, 2026
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