Blog

ColdBox Docs now include cache information.

Luis Majano October 15, 2008

Spread the word

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

I updated the ColdBox docs api to include ColdBox cache metadata information. It was an easy addition and a great one. Now you can use this to actually document your handlers if you wanted and get the extra ColdBox metadata javadocs style. Below you can see a screenshot. docs cache The project used is CFCDoc and can be found at http://cfcdoc.riaforge.org/. To do the metadata update if you use this great project, you will need to open the doctemplate.cfm found in the templates folder. Look for the following line of code: Then you can do your additions like so:
#stComponent.attributes.hint#
Cache: #stComponent.attributes.cache#
Cache Timeout: #stComponent.attributes.cacheTimeout#

 


This works great and you can create your own icons for caching if needed or not. Simple but useful.

Add Your Comment

(2)

Sep 27, 2007 12:54:39 UTC

by Russ Johnson

A nice addition to the best documented framework for ColdFusion!!

Sep 27, 2007 13:06:31 UTC

by Luis Majano

Thanks Russ!! Really appreciate it. By the way, all the guides are being updated this week, with new content, revisions and better UI.

Recent Entries

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026
BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

You call writeDump() on an ORM entity or a very rich class graph . The browser locks up. Thirty seconds later you get a page with forty thousand rows on it, you scroll for a while, you give up, and you go edit your code to dump a sub-key instead. Or worse, you crash the server.

Luis Majano
Luis Majano
September 11, 2026