If you don't know how to update your plugins, just head to the Eclipse Plugins Installation Guide
Railo (www.railo-technologies.com) is a CFML engine that runs on a wide variety of Java servlet engines, and provides a cost-effective, high performance alternative to using Adobe's ColdFusion engine. As you may have heard, at the Scotch on the Rocks ColdFusion conference in Scotland in June, Railo announced that they are partnering with JBoss to convert their software to a completely free, open-source offering.
Gert Franz, CEO of Railo and member of the recently founded CFML advisory committee, will be visiting to present an overview of Railo, and what the advantages of using Railo are for CFML developers. He’ll also be talking about the upcoming open-source conversion of Railo, and what that means for the community and the developers. Of course, Gert will have some free versions of the Railo software to hand out, and some other goodies as well.
Application.cfc - I setup my timeout to 2 seconds, so I can see the onSession end errors come up quicker.
Then I have an index file with the following:
This is mappings Test.
I execute the page, the page executes the component and dumps it correctly. After two seconds I fire up the cf admin and this is what the logs say:
OnSessionEnd : coldfusion.runtime.CfJspPage$NoSuchTemplateException: Could not find the ColdFusion Component or Interface coldbox.system.beans.requestContext.
Now, if I am totally wrong on this one, please comment. However, I do believe the correct behavior would be that onSessionEnd() would respect my per-application mappings. Do you agree?
To solve this, I have to actually create a CF Mapping in the administrator and then it works. But it gets weirder!! Let's say my application is not in the root but here:
I placed a cfc under /testing/cfc/requestContext.cfc. I then modified the code to use this create statement:
And again, it breaks, so it can do absolute references to cfc's either. I moved it to inside the test application and then it works. So there you go, I am totally confused in this behavior. Any comments??
The top 10 concepts are:
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.
ColdBox 2.6.0 is finally out and in final release. You can now download it from the downloads section of the website. This has been a much anticipated journey and it would have not been possible without all the collaboration from contributors, team members and the community. It would take so many lines to thank everybody, but for this release I want to thank Sana Ullah for a TREMENDOUS amount of work and dedication to the team. We also welcomed Matt Quackenbush to the team and more might be joining the efforts soon, especially Ernst van der Linden for always helping out and creating tons of sample applications. So thank you for your time and dedication to this project and making it a true world collaboration project.
As you can see from the image below, ColdBox has become more than just a framework but into a robust application development platform composed of several pieces that when used in conjunction, they can be an incredibly powerful development platform. ColdBox 2.6.0 introduces tons of new features and optimizations that can be read in the What's New Guide in the official wiki site.
I also recommend reading the compatibility guide for pre 2.6.0 applications. This guide will show you if there are any compatibility issues with your application when upgrading. It can show you the workarounds and even guide you from version 2.0 if necessary. Our vision for version 2.6.0 was to solidify our 2.5 features such as caching, interceptions, conventions, stability and tools. We have included more than 100 cfeclipse snippets, an enhanced insight dictionary for both CFEclipse and Dreamweaver, a new eclipse documentation and reference plugin that will help you read all the documentation about the framework's API and configuration file from within Eclipse Help, a new enhanced ColdBox Dashboard with even more code generation features, more cheatsheets and help. There are over 500 pages worth of documentation in the ColdBox wiki, searchable and indexed in such a manner that you can find all the information you need. The entire documentation set has been revised and ready for reading. It has been a long project I undertook more than 2 months ago and finally finalized. The entire documentation is up to date with version 2.6.0 and also prepared for the upcoming versions. Version 2.7.0 has already have a few tickets already assigned and the wheels will be spinning to still provide a community based development environment and help developers around the world create better ColdFusion applications. In summary, thank you for the support and contributions to this project, as they are absolutely of the utmost importance to such a community project.
Also, take note that ColdBox Platform Training Seminars begin this October 4th and 5th in Dallas, Texas. You will be able to register online at our training section of the website and take advantage of our early bird pricing until July 31st. You will be able to get more than 16 hours of training and several hours of QA with us and discuss your specific needs. We are extremely excited about how ColdBox will be able to help your business in the future. So once again, thank you for the support and please enjoy this release.