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
Blog
Recent Entries
Ortus Content Digest for week of August 12th
It's August 12th... what has Ortus been publishing this week? We have the CFML News Podcast, some CFCasts and YouTube Videos, lots of Ortus and ITB Blog Posts. We have a lot more planned for next week as well.
Gavin Pickin
Gavin Pickin
August
12,
2022
ContentBox v5.3 Released
We are so excited to bring you the release of ContentBox Hybrid CMS version 5.3.0. This might be the last release in this major series as we are beginning the push of the next major release of ContentBox v6. Here is our what's new guide with our full release notes: https://contentbox.ortusbooks.com/intro/release-history/whats-new-with-5.3.0
Luis Majano
Luis Majano
August
10,
2022
Want native Redis Support in Lucee/CFML? Ortus Redis Extension v2.0.0 Released!
We are very excited to bring you another release for our Redis Lucee Extension. This is a major release spawning research of over 9 months. We have done great strides in this new extension to not only bring you the best scaling capabilities via Redis, but also now to introduce to the CFML world: Real-Time messaging with Redis Pub/Sub! Here is our full release notes in our brand new documentation book: What's New With 2.0.0!
Luis Majano
Luis Majano
August
05,
2022
Add Your Comment
(3)
Dec 10, 2007 10:43:21 UTC
by Vince Bonfanti
Hi Luis, We investigated this, and it's not really a bug in BD, but a difference in the way CFTHREAD works. BD creates a variable with the name of the NAME attribute, and the "-" character is not valid in a variable name (but we should give a better error message). This is similar to CFQUERY, where a variable with name specified by the NAME attribute is created. Try the following and you'll get an error on both BD and CF: <cfquery datasource="mydsn" name="myquery-#createUUID()#"> ... </cfquery> Out of curiousity, what's the purpose of giving a CFTHREAD a random name? In BD, the NAME attribute is optional, in which case BD will give the thread a system-assigned random name (I don't know if the NAME attribute is optional in CF8). In any case, we're very happy that ColdBox is running on BD 7. Cheers.
Dec 10, 2007 11:04:26 UTC
by Luis Majano
Hi Vince, Thanks for your comment. I think the tricky part of solving it, was that you could not know what the error message meant. So via "Code Smell" the name became the culprit. >Out of curiousity, what's the purpose of giving a CFTHREAD a random name? Yes, the name in CF is mandatory. So I had to create a unique name as a thread is executed by the logger or cache. >we're very happy that ColdBox is running on BD 7. So do I. The performance of ColdBox on BlueDragon is exceptional.
Dec 12, 2007 17:05:36 UTC
by Aaron Roberson
Four days later I check your blog to learn that you've discovered the solution to this "bug". Glad to hear it and great job finding it!