Well, the last beta roundup is here, and yes, it includes the new and improved ColdBox Dashboard. So please enjoy this beta as it includes the following updates and enhancements: - ColdBox Dashboard 2.0.0 - Welcome to ColdBox IoC Object Caching: You can now enable the IOC plugin to cache your service objects in the coldbox cache. In order to do this, you will have to enable it in your config file via the 'IOCObjectCaching' flag. Then, you will need to get rid of your singletons in your IOC declartion files and declare your singletons via the cfcomponet tag using the 'cache=true' metadata attribute. You can also assign a timeout here. - Caching Debugging Panel Enhanced. - Coldspring now receives the coldbox controller reference as part of the settings structure. The gap in the model is now closed. You can now reference the active coldbox controller in your IoC configuration files by using '${Setting: coldbox_controller not found}'. You will now be able to use the framework in your model objects if needed. - AppMapping setting in the config file is now optional. If set in the config file, then it will override the auto-detected mapping. This is a great feature if your main application root is not reachable from the url. - The new object to use in the event handler methods and layouts/views is 'Event' to standardize with conventions. - All documentation updated to 2.0.0 - BlueDragon fixes - Minor fixes,updates. - Install ANT task, so you can refactor the code if needed. - Application Template ANT task. You can now create new applications via ANT. - More guides coming soon. You can find the beta in the forums as usual Well, enjoy this latest beta as the release is coming soon.
Blog
Recent Entries
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.
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.
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.
Add Your Comment
(2)
Mar 18, 2007 07:16:49 UTC
by Sana
Hi Luis,
Its really great work, Would you like to explain one thing. below text from your post:
[You will now be able to use the framework in your model objects if needed].
Thanks
Mar 18, 2007 12:06:31 UTC
by Luis Majano
Sure Sana,
I can actually send the coldbox controller reference into a bean declaration by using the following property in coldspring: ${coldbox_controller}
Once I receive the controller in the model objects I can use it and tap into the framework. Let's say I wanted a setting: coldbox_controller.getSetting()
Let's say I wanted to use the AOP logging tool: coldbox_controller.getPlugin().logEntry(,)>
Now, some people will say, then you tie your object model to a framework. Well, the answer is YES!! That is my purpose, to extend into the object model and take over.
There are so many good things about it, I am using it anyways. So If I ever decide to go to another framework, probably means, ColdBox is not around anymore.
So expect more object model infiltrations by coldbox.