Blog

Well, I have been finally going at it more than usual to get this public beta out. You can find it now under my projects section by using the link below http://www.luismajano.com/index.cfm?event=ehProjects.dspColdbox So welcome to ColdBox. Please use the trac site for issues and the wiki, which I have been putting a lot of content. Use the forums for any discussions, and if you need to contact me use the conta...

Well, I am finally opening the lid on a project I have been developing since August of last year: ColdBox a ColdFusion Framework. I am just releasing the specs for this framework for now as I complete all the documentation and sample applications. If you want to see how it works, well you are already using it. This site, its blog (Raymond Camden's BlogCFC by the way), and its forums (

On my last post, Sami Hoda, pointed out the following:

How about an architectural comparison between Coldbox and other frameworks to give existing frameworks people perspective?

And I think it is a great idea to give reference on what ColdBox can do and how does it compare to other frameworks. However, I do need some help from you (Developers) to post exactly what you want to compare. I can ramble and ramble, but I would prefer to get a listing of wh...

In preparation for the 1.1.0 release of ColdBox, I am writing documentation like crazy so I can help developers understand more on how to use this framework. I have just finished all of the Guides and a new section which actually lists all the thrown exceptions by the framework. You can take a look at the list here: Exceptions List Guides: Guides FAQ ...

I just realized that I got nominated to speak at the Frameworks Conference in DC in February. So if you really support ColdBox and would like a ColdBox 101 session for this conference, then go to the link below and vote for me. http://www.frameworksconference.com/survey.cfm Thanks again for your ColdBox support.

I just created the ColdBox Google Groups Mailing List. You can use it for solving issues, bugs, discussions or anything you like. Also, if you forward any messages to bugs@coldboxframework.com and it is a valid bug it will be started as a discussion also if need be. Here is the info:

• Group name: ColdBox: A ColdFusion Framework
• Group home page http://groups-beta.google.com/group/coldbox
• Group em...

I recently found some great comments about a user commenting on ColdBox, why it exists, why create it, etc. I found it enlightening because, not many people have used this yet, it is fairly new to the open source community and it is my job to write more about the nature of ColdBox and using a coldfusion framework. So to introduce the article I have to note that ColdBox is another tool for web application development. Just like mach-ii and model-glue. Some people want competition and which one is the best. I do not believe in that. I believe in cooperation and finding the best solution to a problem, no matter what. I even wish that all the framework authors can join and create a solution. (Anybody listening?? A standard??) So please understand, that object oriented approaches and enterprise level application architectures will be complex and you should study upon them. Here is my article:

I have had some suggestions for the fwreinit flag to be protected in order to reinitialize the application at hand. What do you think? Is this overkill? The application reinitializes, but it does not crash. It just adds some extra cycles to the request in order to clear and reinit the app. Please send me your comments, suggestions? Should an application reinit, be password protected? Thanks, Luis

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)

This is a question for you to answer. ColdBox supports the mode of being in debug mode or not. It does so, by placing a cookie on your browser so you can see the debugging panel only with that cookie set. The question is, how long should that cookie live? What should the expiration time be? Any suggestions?