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
One Language, Every Runtime: BoxLang Expands Beyond the Server
Discover how BoxLang’s multi-runtime architecture helps developers build beyond the server with support for serverless functions, desktop applications, CI/CD workflows, Java integrations, containers, runtime management, and more.
MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge
The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.
That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.
BoxLang 1.14.0 : BoxSet is Here: BoxLang's New First-Class Set Type
BoxLang 1.14.0 ships something that JVM developers have wanted for a long time: a true first-class Set type baked directly into the language. Not a wrapper you reach for manually, not a createObject( "java", "java.util.HashSet" ) incantation you paste from a Stack Overflow answer years ago. A real BoxSet with literal syntax, operator overloads, a full functional pipeline, change listeners, JSON serialization, and deep Java interop.
Add Your Comment