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
Hackers demand a ransom to restore data from my ColdFusion web applications!
Hackers demand a ransom to restore data from my ColdFusion web applications!
Unfortunately, we often hear this message from clients who thought it would never happen to them... until it did. Some believed they could delay the expense of Implementing ColdFusion security best practices for one year, while others were tempted to put it off for just a few months. However, in today's rapidly evolving digital landscape, the security of web applications, including ColdFusio...
Ortus March Newsletter
Welcome to Ortus Solutions’ monthly roundup, where we're thrilled to showcase cutting-edge advancements, product updates, and exciting events! Join us as we delve into the latest innovations shaping the future of technology.
Into the Box 2024 Last Early Bird Days!
Time is ticking, with less than 60 days remaining until the excitement of Into the Box 2024 unfolds! Don't let this golden opportunity slip away; our exclusive Early Bird Pricing is here for a limited time only, available until March 31st. Why wait? Secure your seat now and take advantage of this steal!
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.