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
A Year in Review - BoxLang 2024 Recap!
BoxLang has come a long way since its beta release, and we're thrilled to share the incredible progress made so far. From its initial launch to the upcoming stable version, BoxLang has been evolving with new features, tools, and a growing ecosystem, all aimed at empowering modern developers.In this recap, we’ll highlight the milestones and advancements that have shaped BoxLang’s journey to this point. Let’s take a look at what we’ve achieved and what’s coming next!
Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!
At Ortus Solutions, we’ve always been at the forefront of innovation in the ColdFusion ecosystem. From pioneering modern ColdFusion practices to developing cutting-edge tools and frameworks, we’ve been passionate to help and sup[port the community into shaping the future of web development.That’s why we decided to build BoxLang, our new JVM programming language that not only builds on the strengths of ColdFusion but takes modern software development to the next level.
Ortus Solutions & BoxLang at Jfokus 2025: Silver Sponsor and Innovator
We’re thrilled to announce that Ortus Solutions, through BoxLang, will be participating as a Silver Sponsor at the prestigious Jfokus 2025 conference! Taking place in Stockholm, Sweden, from February 3 to 5, Jfokus is one of the premier developer conferences in Europe, bringing together thousands of tech enthusiasts, thought leaders, and industry professionals.
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("AppMapping") Let's say I wanted to use the AOP logging tool: coldbox_controller.getPlugin("logger").logEntry("info","I am logging from my model object")> 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.