Category Filtering: 'ColdBox'
I just want to thank the entire ColdBox team for their work and perseverance in this great project. Keep up the good work guys!!
Anyways, he wrote a cool guide on how to activate it and it is very simple. Please go to his blog and read this article.
I want to welcome two new members to the ColdBox Team today, Tom de Manincor and Ernst van der Linden. Their dedication and contributions to the project have been incredible over the years. We are also good friends and best of all we where all in different locations. Tommy is now living in California, but before he was all over the place :). Ernst is from The Netherlands and talk about world collaboration. I am truly excited that our commitment to this project is strong and growing. We are producing some very exciting new funtionalities and tools to help developers achieve their goals even faster. The future of ColdBox is bright and shining like ever before.
Let me start with Tommy. I met Tommy at my previous employer and he was one of the pioneers of the first non-public versions of ColdBox. He was involved with project direction and implemented several projects using our first iteration framework. Over the years he has truly become an OO guru and keeps pushing things to the limit. His New York accent and attitude always comes out and its always funny to talk to. We are currently working on some cool cluster communications and messaging that will become available for ColdBox in the near future. Welcome aboard Tommy!!
I met Ernst online, like we all do. He has been a big advocate of ColdBox since day 1 and he produces some incredible software applications with it. He has been contributing to ColdBox in all areas of development, from testing, bug reporting, sample creations, architectural and design issues and our new top secret project called: Project SideBar, which will be announced in the coming months. So welcome aboard Ernst.
Below are the bios and links:
Tom de Manincor - http://www.tomdeman.com/blog/
I have been working with ColdFusion since 4.5 Express was released. Its been a pleasure to develop in a language that has grown to be so powerful. I had the luxury of working with Luis Majano, creator of Coldbox framework, back in 2004. A great educator and programmer. Who introduced me to another great mentor of mine, Rob Gonda, creator of AjxCFC. Another very talented and knowledgable resource. Like them, I share a passion for my work, and a pride in sharing it with the community. I have developed in mama's spagetti code, a handful of frameworks, and everything in between.
As of late, I have been focusing my efforts on Object Oriented programming with Cold Fusion. I try to learn as much as I can about design patterns, best practices, and new ways to blow my mind with code.
I am currently the Lead Developer with Blush Media, LLC out in El Segundo, California. Developing a number of applications in Coldbox, Coldspring, and Transfer.
Ernst Van der Linden - http://evdlinden.behindthe.net
A software architect: primarily using ColdFusion and Java in combination with SQL databases.
Began programming in 1988 on a Commodore 64 and started with Coldfusion in 1996. He has designed applications for companies such as General Electric, Philips and Shell.
In 1999 Ernst van der Linden launched his own software company BehindThe.net which builds HR Management Software for multinationals.
If you don't know how to update your plugins, just head to the Eclipse Plugins Installation Guide
Thanks
I am releasing today a set of addons for ColdBox-Transfer interactivity:
You can download these tools from here. All you need to do to install them is drop them in the /coldbox/system/extras folder. This will create a transfer folder that holds these cfc's inside of the extras folder. That's it. Then you need to configure them via a coldspring.xml or a lightwire configuration object or manually (ohh brave one). The tools have also been added to the SVN and I will be adding a link to them from the extra downloads section of the website.
This object is used to create a transfer configuration object based on the datasource information found in the ColdBox configuration file. This idea is thanks to Tom de Manincor and his musings in ColdBox-ColdSpring-Transfer. This let's you maintain all of your application's configuration in one single location and not create a datasource.xml. It is meant to be used alongside coldspring but it can be used as a separate object too (You will have to do the wiring). Anyways, here is a sample coldspring declaration for this usage:
As you can see, we first define the coldbox factory element and construct a datasource bean element with it. We then setup the transferConfigFactory.cfc as a coldspring factory bean. The last step is configuring the transfer factory. We send in a configuration bean and set it up as a call to our transfer config factory with the same parameters we are used to, except that for datasource we use the dsnBean element and have it referenced to the datasource that we want to use, in our case MyDSN, that we defined at the beginning. If you need a refresher on how the ColdBox Factory for IoC works, please read the following IoC Integration Guide. That's it. Simple as that, now you can define all your configurations via the coldbox configuration file and let coldspring do the heavy lifting.
This handy tools is based on Brian Kotek's original observer. I want to say thank you to Brian for his contributions and incredible code. Thanks Brian.
However, we have modified it to use ColdBox beanFactory plugin to do the autowiring for us. For those familiar with the ColdBox autowiring conventions, you can do autowiring via annotations using the cfproperty tag or via setter injection. Not only that, but you can use ColdSpring or Lightwire seamlessly, and to top it off, you can autowire objects from the ColdBox cache. Here is a sample of some cool autowire annotations:
As you can see from the code we have two dependencies marked by their types: ioc and ocm. The type of ioc means that this dependency must be injected from the ioc plugin (coldspring/lighwire) and the type of ocm means that the dependency must be injected from the ColdBox Cache. The scope attribute is also useful as you can define in which scope or pathed scope you would like this dependency injected. The default value is variables.
The theory behind this tool is to be able to very easily create rich decorators that can be injected with dependencies from the IoC container or the ColdBox Cache. It is a great way to have your objects be composed of other objects and utilities. So let's see the coldspring.xml, but first, please note that the instructions below are for ColdSpring 1.2 that enables the usage of the lazy-init property. For Coldpsring 1.0, you will have to do some more manual work. (More instructions found in the cfc's themselves).
We first define the ColdBox Factory, then the beanFactory plugin we will use. We then define our Observer with some cool parameters:
That's it folks. Once application starts up, coldspring will create and register this observer for you. So when transfer objects are created and have autowire dependencies, they will be wired up.