Coldbox Download Error, My Apologies
Enjoy
Category Filtering: 'ColdBox'
Enjoy
It also includes a fix for the CustomException Handler, it now has the exceptionBean in the request collection for usage if needed. Code cleanup and removal of unused files that escaped my mind.
A good note about the CustomExceptionHandler receiving the ExceptionBean is that you can determine the type of error and determine what to do with it.
For example, all of the framework internals throw certain types of errors that can be handled by this exception handler. ( ExceptionBean.getType() ) One that I use very often is:
Framework.EventSyntaxInvalidException
You can use this if the event being passed via the url is incorrect.
Framework.EventHandlerNotRegisteredException
You can use this if the event that is tried to be executed is not a registered handler in the framework. You can then proceed to redirect or do the necessary steps to deal with this exception.
I will be posting this revision on Friday. I would also welcome your feedback, you can comment here on this Blog, or use the Forums or just email me at [email protected]
Enjoy
Also, the samples gallery application is in Spanish.
I will be updating all the documentation to Spanish too, but it will take me some time. I really would appreciate your feedback on typos or sentences that really do not make any sense or if you want to help me translate, well,you are more than welcome.
You can download the ColdBox public beta 1.0.0 from here:
http://www.luismajano.com/projects/coldbox
Enjoy.
You can download the update, or you can use the auto-update feature of the dashboard.
So give that auto-update feature a spin and let me know if it blows up.
http://www.luismajano.com/projects/coldbox
Enjoy.
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 contact button in the nav bar or email me at [email protected]
The disto includes several sample applications, some of which were not created by me. So please respect the authors licenses and rights.
Thanks and hope you enjoy.
Well, it is almost a week since my announcement of ColdBox and here are the updates on my progress.
What is keeping me back from opening the source is the Quick Start Guide. I want to be able to provide some decent and abundant documentation, so from now on, that is the only task I am doing. This guide will give you an overview of the framework, how to use it, why use it, why not to use it, and more.
Now to the Dashboard preview. Below you can see some thumbnails of the sections of the Dashboard and brief descriptions:
ColdBox is a proven event-driven CFC based ColdFusion Framework, specifically designed for high availability web applications. The purpose behind ColdBox was to create a fast & stable development methodology that could be shared among several developers. It makes use of an MVC (Model View Controller) design pattern implemented via CFC's. I introduce the concept of event handler CFC's that hold all the code necessary to prepare views, call model CFC's, use ColdBox plugins, and redirect requests through the ColdBox Controller. You can consider the event handlers to be all that code that you had on top of your templates, but now moved to an Object Oriented pattern. You can look at the MVC Design Pattern diagram below:
ColdBox uses both implicit and explicit invocation methods. You have one single xml file: config.xml, from where you can configure your entire application and plugins. You can use ColdSpring, Reactor, Remoting, CRUD, Bean/DAO Factories or any other technology and/or pattern that you can think off with ColdBox. However, ColdBox does make you adhere to an application directory structure and some naming conventions. This is done with the purpose of creating a standard for all developers in the same team to share and for ColdBox to find what it needs. You are only limited by your ingenuity.ColdBox also uses a request collection where all variables can be shared among an execution request. The Request Collection is a central repository of information that is refreshed on every user request. This is how data gets moved around from event handlers to views and layouts.Another important feature is the use of a plugin library of CFC's that extend the normal usage of ColdBox to application specific tasks but without hindering system performance. These plugins are reusable components that your applications can use for application-specific tasks and can be loaded on demand via a Plugin Factory. Thus, your plugins are not utilized or loaded into a scope, they are just invoked. Some samples are: i18n, resource bundles, refresh a webservice stub, Bug Reports, java file utilities, etc. This is a major difference between ColdBox and any other framework, in that it gives you a set of reusable on-demand components for tedious or repeatable application-specific tasks.Below you can see an overview diagram of how ColdBox works, you do not need to install special software on your web server or radically modify your coldfusion installation. You can explore this site to find more information about ColdBox. If you need to contact me please use the Contact button in the navigation bar.
ColdBox Overview:
ColdBox Capabilities & Features
Hope this can give you a better insight into what ColdBox is and what it can do. I will start posting more information as I progress.