Blog

I have just spend some good time working on a revamped guide that will truly help the ColdBox newbie digest and get a hands on approach. You can reach it by clicking me here. This guide covers the application template and ANT generation scripts that ColdBox provides. It will be further enhanced once the application generator is finalized in the ColdBox Dashboard. Please give me your thou...

Catchy and corny title, right? Well, get your mind out of the gutter now and welcome another new guide for you Ajax Masters!! ColdBox & Ajax In a Tree, K-I-S-S-I-N-G!! It might be a short guide, but it sure is sweet!! Ok, enough with these corny references. Hope you enjoy it.

As with the new 2.0.1 release from yesterday, you now also get a new Refactoring Guide. This guide is a step by step guide on how to refactor ColdBox for use in your own custom server environments, shared environments or even embedding ColdBox in your commercial applications. Open The Refactoring Guide If you would like to add anything to this guide, please let me...

Adam Fortuna created a post on a technique to automatically assign default views to your application, which is very very interesting. I also posted an alternate way of assigning default views/layouts to even any handler by just creating and implementing a preHandler or postHandler method on your handler. Great Snippet ...

Russ Johnson has just posted this very in depth guide that you have to check it out!!

Russ Johnson has just posted this very in depth guide that you have to check it out!! He describes his process when migrating his applications to ColdBox from fusebox. This guide deals with migrating views.

Well, my secret project is out of the bag today. I have been working in embedding a remote proxy into ColdBox in order to enable remote applications like Flex and AIR to communicate with ColdBox and provide an event model for our model. If that makes sense!! Well, so what do we get? This feature lets you create an event driven model that can easily be called from any flex/air application. Not only that, but you can reinitialize the entire application, get settings, and yes, announce custom or core interceptions. You can create custom interceptor chains for your model that can be executed asynchronously when a user hits a save record button for example. The possibilities are endless. Not only that, but this enables you to actually create two front ends using the same reusable ColdBox and model code. The code is the same, you create event handlers, you interact with a request collection, with core and custom plugins, but you don't set views or layouts because the framework is now a remote framework for your model. So what do you do, well, return data, arrays, xml, value objects. Anything, right from withing the event handlers.

Keep a close eye on the wiki as all the documentation is getting revamped and updated. I am about 75% done with all the new docs and guides. Here is just a brief overview of the new guides:

Matt Quackenbush submitted this unusual behavior a few days ago and I was finally able to reproduce and fix today. Here is his excerpt:

If I browse to http://localhost/myApp/index.cfm/main/dspHome (or any other explicitly-called event), everything is good to go. However, if I browse to http://localhost/myApp/ or http://localhost/myApp/index.cfm, an exception is thrown that says: The event handler: index.cfm.dspHome is not valid registered event.

The ColdBox interceptors guide has been updated with some new cool approaches on how to deal with interceptor dependencies and their life cycles. You can see how they get created and configured so you don't go in loops to know the actual process. The injection of dependencies is also demonstrated when using an IoC framework like ColdSpring/Lightwire and even when you are not.