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
MatchBox Brings BoxLang to ESP32 Microcontrollers 🦀
One of the most unusual parts of MatchBox is the ESP32 target.
The MatchBox open beta is available at https://github.com/ortus-boxlang/matchbox, and it can compile BoxLang scripts into bytecode and deploy them to ESP32 microcontrollers. That means the same language used for scripts, native tools, web services, and browser logic can also run on a small embedded device.
Jacob Beers
Jacob Beers
June
15,
2026
BoxLang AWS, Azure, and Google Secrets Manager Module Released
Every production application carries secrets: database passwords, API tokens, encryption keys. The question is never whether to manage them -- it's how badly the current approach is going to hurt you.
Luis Majano
Luis Majano
June
15,
2026
BoxLang 1.14.0 : BoxLang Ranges Part 2: Teach BoxLang Your Types with `IRangeable`
In Part 1, we covered BoxLang's first-class range system: lazy evaluation, exclusive boundaries, built-in types (integers, decimals, characters, dates), custom stepping, Java Stream integration, and contains() semantics. If you haven't read it yet, start there.
Luis Majano
Luis Majano
June
15,
2026
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= name=>
...
</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 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 . Glad to hear it and great job finding it!