Trying to decide whether to use ColdFusion's EHCache implemention or CacheBox? You don't have to choose one or the other! CacheBox is a cache aggregator, which means it lets you use the same standard API to interact with any number of different cache providers-- including EHCache.
To configure an EHCache provider in CacheBox (assumming your using Adobe CF 9.0.1 and up, of course) add the following struct to the "caches" object in your CacheBox config.
myCoolCache = {
provider = "coldbox.system.cache.providers.CFProvider"
}
That's it!
Now you can grab that cache by name from CacheBox and start using it:
cacheBox.getCache("myCoolCache").set("myKey","myValue");
cacheBox.getCache("myCoolCache").get("myKey");
More info here: http://wiki.coldbox.org/wiki/CacheBox.cfm#CF_Providers
P.S. Please note that you can configure more than 1 CFProvider cache engine in your applications that can talk to more than one referenced ColdFusion (EHCache) custom cache. Just use the cacheName property to tell the CFProvider which EHCache instance to use.
Blog
Recent Entries
Introducing BoxLang AI Explorer: A Local Catalog for Every AI Pattern
Learning a new AI API usually means jumping between scattered documentation pages, guessing at imports, and copy-pasting code that may or may not still work. We wanted something better for BoxLang AI, so we built the BoxLang AI Explorer: a local, browser-based catalog of runnable BoxLang AI examples, organized by category and difficulty, each with guidance, source code, and sample output.
BoxLang at Florida International University: Supporting the Next Generation of Modern Devs
The future of software development depends on more than the technologies we use. It depends on the people who learn to use them, improve them, challenge assumptions, and apply them to real-world problems.
Community Spotlight: BoxLang Express Brings Node-Style HTTP to the JVM
If you've spent years in Spring Boot, Micronaut, or Jakarta EE, "web framework" usually means a servlet container, an embedded Tomcat or Netty, a build step, and a fat jar before anything answers a request. What if you could skip all of that and still be on the JVM?
Add Your Comment