Blog

Hi Folks! I was just informed by my Trac host that I now have PDF generation on the wiki. So I just wanted to share the good news. You can find the trac site at the following address: ColdBox Trac Site

So now you can download the content in PDF. Just scroll all the way down to the bottom of the page and you will see the "Download in other formats: Plain Text | PDF"

Now you can archive the docs. Thanks.

Below you can find a link to the last know issues for the 1.2.0 beta release:

Last Known Issues

And you can also subscribe to it via RSS through the link below:

Last Know Issues RSS Feed

Thanks again for your support and hope to hear some feedback from you guys. Please be patient with me as I update the docs for this release. So keep checking the timeline feed as progress continues.

Finally you can test drive the up and coming ColdBox 1.2.0. There are so many improvements and enhancements to list here.

Below is a sample of the readme. The most notable improvements are IoC integration (coldspring/lightwire), ColdBox in-memory caching manager for event handler caching, plugin caching, custom plugin caching and custom data caching (Event template caching is coming...). The cache is unique, since it displays in the debugging panel the effectiveness of the cache in hits and misses, the amount of items in cache, what items are in the cache, and the reaping parameters. Event handler packages, datasource aliases, and much more.

1.2.0 Milestone Information

I will be updating all the guides this week for 1.2.0, so please be patient with me as there is considerable documentation for this release.

Please look at the samples gallery, and the most notable is the ColdBoxReader. It has been updated to a services architecture and also uses ColdSpring and ColdBox's new IOC plugin, so please check it out.

Well, just head out to the forums to get your brand new 1.2.0 beta.

Click here for the 1.2.0 Beta

Please make sure to posts you comments and suggestions in the forums, also the bugs. This is important. I need your feedback.

I will be posting more information in the coming days. So stay tuned.

The new cfc api for the framework is now available at http://www.coldboxframework.com/documents/cfdocs/ Please head over there to see all the documentation on the new methods, etc.

As always, please report any bugs on the forums or to [email protected]

I had forgotten to extract some documentation from the compatability guide that is no longer in play for the beta. If you have started to read the guide, please do so now. I have updated the wiki and the pdf in the download.

My good friend and collaborator Aaron Conran, just posted a very interesting article on how to migrate your fusebox apps to coldbox. Also it explains some of the benefits you achieve.

You can find the article here

Transitioning from Fusebox to ColdBox

This is more of an announcement of the upcoming 1.2.0 features.

Since event handler caching will be instilled into the framework, the

performance is dramatic. It actually, does not make sense to be

creating event handlers for each request. So version 1.2.0 will be the

last version to support uncached handlers. The versions after 1.2.0

will have caching of handlers by default. I see no benefit of

not caching the handlers. And they can easily be recreated by using

fwreinit= url command

So. Since event handler caching actually changes A LOT in event

execution. The methods will receive the request collection object,

instead of the handler being injected with it at creation. What does

this imply? Well, mainly the 'rc' scope will become deprecated. You

can keep it, however, you must var scope it locally.

Example:

var rc = arguments.oRC (or whatever the argument is named, still

pending)

For those of you interested in testing the upcoming 1.2.0 ColdBox release, please download it from the repository and give me your feedback. I have just finished uploading a stable version. Some of the new and interesting features are the following:

ColdBox Event Handler Caching

If you thought that ColdBox was a fast framework, well it just got faster. With the flick of a new setting HandlerCaching your application will cache the event handlers. This opens incredible opportunities for actually making your handlers into objects with more specific functions and processes. You can now implement an init method on them and instantiate services on them, etc. The possibilities are endless. NOTE: The init method's if implemented, will need to call super.init() mandatory. Look at documentation.

From some load testing I have done, I have seen execution improvements of around 35-40%. Which is extraordinary. Plus, it is Thread Safe. So you can implement AJAX interactions with peace of mind. So give them a test, you won't regret it.

ColdBox Event Handler Packages

This is a great feature in order to get ready for the 2.0 release. This enables the developer to actually create packages for your event handlers. So re usability and organization are expanded. You can create in your handlers directory a handler package for blog operations, for logging operations, etc. This is great if you want to place two,three, a thousand ColdBox applications into a single application. You will just create packages and place your handlers in specific package. The new ColdBox event registration system will find them and register them. You can then package your views and layouts. Multi-applications with one single configuration and structure. WOW!!! Ohh by the way, there is no long XML dialects in order to glue the events. Its pure ColdFusion, like it should be.

ColdBox for Compiled Code

Due to ColdBox's 1.1.0 event registration system, compiled applications would fail. NOT ANYMORE. The new registration system will now work with compiled code. Even more, you can even compile the framework. (Just make sure the config.xml.cfm's are not compiled, they are XML files not cfm)

Auto populate beans from a Request

This great feature was brought to you thanks to Sana Ullah. The beanFactory plugin now enables you to populate a named or instantiated bean with a request's data (request collection). So If you are using a IoC framework like Lightwire or ColdSpring. Then you will definitely benefit from the framework actually populating your beans without you doing it. Here is a cool snippet:

That is it. The bean is ready for update/delete/etc.

---

As always, this is still in development. So please give me all the feedback you can. You can find more on what features are coming, what bugs where fixed at the usual Trac Project site: http://ortus.svnrepository.com/coldbox/trac.cgi

There are also a few surprises coming to the 1.2.0 release which I will not discuss until they are done. Just let me say, that It will truly make ColdBox a Swiss Army Knife, like Mr. Gonda refers to this framework!! (You will like this one!!)

You can head over at CFDJ for a great frameworks article by Faisal Abid : Frameworks, Frameworks, Frameworks

http://cfdj.sys-con.com/read/317576.htm

It talks about why frameworks should be used, their role and how they can help application development. The article mentions ColdBox and some of its features.

I just opened the announcement of ColdBoxReader. A coldfusion based RSS reader that comes included with the ColdBox Bundle. I will be separating this project and enhancing it according to community needs. So please give your opinions and suggestions on this project. As of now, it is part of the ColdBox project and will continue in its same timeline.

The link is http://coldboxreader.riaforge.org/

So please enjoy and bring me your comments and suggestions. Ohh, by the way, here is a demo URL

http://www.luismajano.com/coldboxreader