There have been some bug fixes and patches to 2.6.2 that can be located on our daily build and SVN.  If you are curious of what these bugs are and how milestone 2.6.3 is shaping up, please go here and check it out.

2.6.3 will be our last maintenance release in our 2.X ColdBox Series before we start development on ColdBox 3.0.0 which will be a nice move ahead from our past 15 versions.  We have tons of exciting updates, surprises and performance updates for our 3.0.0 version.  You can also check out how this release is shaping up by visiting the milestone here.

I have been getting several reports about IllegalStateExceptions from several people now and wanted to have this documented to help other ColdBox or ColdFusion developers out there. Have you been getting any IllegalStateExceptions in ModuleTag on your ColdBox Applications?? Are you using ColdFusion 7? Well, Adobe has a hot fix for this bug and it has been an old issue and of course, resolved in ColdFusion 8.

Adobe has resolved an issue with IllegalStateExceptions thrown intermittently by ModuleTag. The stacktrace generated is similar to the following: java.lang.IllegalStateException at coldfusion.tagext.lang.ModuleTag.doAfterBody(ModuleTag.java:439) at cfindex2ecfm842540228.runPage(C:InetPubwwwrootIllegalStateExceptionindex.cfm:18) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:349) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:219) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:51)

The scenario where this problem occurs typically includes the following items: 1. Use of an application framework. 2. Use of Application.cfc and OnRequestEnd or OnSessionEnd method. 3. Calling methods on ColdFusion Components stored in shared scopes, often the application scope. 4. The use of custom tags. Secondary issues caused by the IllegalStateException are often resolved by application of the patch. These issues have included query truncation and invalid parameter binding errors with cfquery and cfqueryparam.

Matt Quackenbush submitted this unusual behavior a few days ago and I was finally able to reproduce and fix today. Here is his excerpt:

If I browse to http://localhost/myApp/index.cfm/main/dspHome (or any other explicitly-called event), everything is good to go. However, if I browse to http://localhost/myApp/ or http://localhost/myApp/index.cfm, an exception is thrown that says: The event handler: index.cfm.dspHome is not valid registered event.

Read more...

I am so happy to announce that the last bug for BlueDragon 7 on ColdBox has been resolved. It was tricky, but it all came down to using "-" on the name of the thread being created. If you have something like: ... This would fail parsing in bluedragon 7 but work as normal in Adobe CF. So I had to replace and come up with better names: ... And voila!!! It works!! So the final bug registered for ColdBox RC 2 has been resolved. Hopefully, no more bugs will creep up. If you have any, then send them in. As of now, THERE HAVE BEEN NO MORE REPORTED COLDBOX RC2 BUGS. This might cause a release soon!! Luis

I just realized that the compilation under cf8 will not work in cf7. Therefore, I will have to alter my compilation scripts to do cf7 and cf8 compilations for the Dashboard. Expect an update for the dashboard in the RC1 package by the end of the weekend. This should be easy to setup so I can deliver a cf8 and cf7 compiled dashboard.