We have now released version 1.8 of the ColdBox Platform Utilities extension for ColdFusion Builder.  This version brings in some cool new stuff and some fixes for auto updates and ForgeBox connectivity.  We are already planning the next version with some more cool stuff coming your way.

Version 1.8

• Update to application templates to new 3.0.0 M5 standards
  
• Update to code generation templates with some fixes on old code
  
• Generation of ColdBox Integration tests. You can now generate integration tests a-la-carte
  
• Fixes for security generator when generating interceptor code
  
• New menu contribution: ColdBox ForgeBox to provide a tighter integration to ForgeBox
  

We have now released version 1.6 of the ColdBox Platform Utilities extension for ColdFusion Builder.  This 1.6 updates almost all of the assets and internal templates for some nice refactoring.  You can use the auto update features if you like, however, we recommend for this release to do a manual override, as there are several things that need to removed also.  The upcoming releases will be more stable in terms of auto-updating.  Or if you are adventurous, just click on the Auto Update features and voila done!


Version 1.6 Updates

• Lots syntax updates and refactoring
• Addition of css/js and jquery assets
• Install from ForgeBox by slug entry.  You can now very easily install ANY entry from ForgeBox by just using its unique slug
  
• Lots of updates for setting up interceptors with or without programmatic configurations

Self admittedly, I am new to Unit Testing. It is on my list of things to learn and implement into my development toolbox and workflow for 2010. So, officially, I have begun the process using the Base Test Case ColdBox has built in and the illustrious MXUnit of course.

All my testing was working great until I wanted to test something that was using CF9 ORM/Hibernate integration.

The first issue I had was that ColdBox creates a separate application for testings. That is, the test folder has its own application.cfc defined. Well, obviously by default, that application.cfc doesn't have ORM setup, which then of course caused me not to be able to test anything that relied on or used an ORM "persistent=true" cfc or did an EntityLoad or anything like that.

So, the workaround for this issue is pretty simple.

First, open up the application.cfc in the test folder, then setup a mapping to your base application your testings. Call it whatever you like, I called my mapping baseApp.

this.mappings["/baseApp"] = expandpath('../../');

You can change the pathing to match your given scenario.

Then you need to configure orm in the application.cfc.

this.ormenabled = "true"; this.datasource = "MyDSN"; this.ormsettings = {cfclocation=["/baseApp/model/ORM","/baseApp/modules"]};

And there you have it, ORM is now configured for your testing application and you can test away.

Read more...

We have now released version 1.5 of the ColdBox Platform Utilities extension for ColdFusion Builder. As you might now ColdFusion Builder was also released this week and I am super excited as the extensions capabilities are just outstanding for a 1.0 release. This 1.5 updates all the application templates and now also the ColdBox Modules templates. But wait, there's more! You can now auto-update the extension right from builder. We have added the capability to check for new releases of the extension via ForgeBox and if there are any updates you can choose to install the update and voila! New Extension Installed.

On the spirit of non-stop releases, here is LogBox version 1.2.  Apart from some bug fixes we have squeezed in some great new functionality, especially when dealing with configuring LogBox and portability. Check out our milestone tickets for further review. Version 1.2 Tickets

• Added some new methods to the LogBoxConfig object: resetAppenders(), resetCategories and resetRoot() to reset some configurations.
• Fixes on appender declarations and layouts
• Addition of the LogBox DSL to coldbox configuration file, so now you can configure logbox via a cool DSL
• Ability to configure LogBox via a simple CFC with a simple configure() method and our cool DSL

The major portion of this release is three words "Portabiity in Style".  We wanted to add a new way to configure LogBox in ColdBox style, a cool data definition DSL. Of course, our documentation is updated and now online: http://wiki.coldbox.org/wiki/LogBox.cfm#LogBox_DSL. Here is a little tast of the DSL: function configure(){

logBox = {
   // Appenders   appenders = {
      appenderName = {
         class="class.to.appender",
         layout="class.to.layout",
         properties={
            name = value,
            prop2 = value 2
         }
   },
   // Root Logger   root = {levelMin="FATAL", levelMax="DEBUG", appenders="*"},
   // Granualr Categories   categories = {
      "coldbox.system" = { levelMin="FATAL", levelMax="INFO", appenders="*"},
      "model.security" = { levelMax="DEBUG", appenders="console,twitter"}
   }
   // Implicit categories   debug = ["coldbox.system.interceptors"],
   info = ["model.class", "model2.class2"],
   warn = ["model.class", "model2.class2"],
   error = ["model.class", "model2.class2"],
   fatal = ["model.class", "model2.class2"],
   off = ["model.class", "model2.class2"]
};

}