1.0.0-Beta3
June 28, 2024
Last updated
Was this helpful?
June 28, 2024
Last updated
Was this helpful?
BoxLang Betas are released weekly. This is our third beta marker. Here are the release notes.
Thanks to our enterprise cache engine and aggregator built into BoxLang, you can now use it to cache queries via its options
configuration structure using cfquery
or queryExecute
. Here are the query caching properties you can use:
cache:boolean
- To turn on caching, this must be true
. The default is false
cacheTimeout:timespan
- Optional timeout of the query in the cache. By default, is uses whatever the default timeout of items the cache has been configured with.
cacheLastAcccessTimeout:timespan
- Optional last access or idle timeout of the query in the cache. By default, is uses whatever the default timeout of items the cache has been configured with. This means that if this query is NOT used or requested in this timespan, it will be marked for eviction.
cacheProvider:string
- The name of the cache provider to store the queries. By default, we use the DEFAULT
cache in BoxLang.
By default, queries will use , which has default timeouts and lastAccessTimeout
values set.
To specify a custom caching provider, you can use the cacheProvider
query option:
To specify custom cache entry timeouts, use cacheTimeout
or cacheLastAccessTimeout
:
All query metadata will also have the cache information available to you as well. So you if get dump the query metadata you will see a ton of debugging information about the query:
Please note that this leverages the BoxLang cache. This means you have full access to the cache provider and you can interrogate it for queries, clear all of them, or clear one of them. The default prefix used for all cached queries is: BL_QUERY
This is another major milestone in the Java interop features of BoxLang. This allows us to coerce any BoxLang Lambda/Closure/UDF or even Classes to ANY, yes, ANY Java Functional Interface or Java SAM (Single Abstract Method Interface).
Virtual Threads are now available to BoxLang via executors. You can choose the new VIRTUAL
executor for schedulers or when creating schedulers via our AsyncService. This will treat all tasks and schedules to use virtual threads.
More entry points to access this executor will be provided in the coming betas, alongside our very own runAsync()
and the ability to create virtual threads as well.
As more modules are being developed for BoxLang, you now have the ability to know which modules have been loaded and activated in the language. As well as specific information about a module if needed. This is great for inter-dependencies and checking if modules have loaded from BoxLang.
This is a developer eye-candy, so when you dump any Java class, you can actually see the value of the class instance data via the toString()
method.
The dumping of BoxLang Functions (Closures, Lambdas, UDFs), either standalone or from a class, has great visibility now. You can see even the class used to generate the function, the function annotations, and much more.
If you use createDynamicProxy()
to make a BoxLang class look like a Java class, you can continue to do so now, but it accounts for all class loaders in the application. If you come from a CFML engine, this is impossible and is always a pain and limitation.
In BoxLang, your context matters. So depending on where you create the dynamic proxy, it will account for the surrounding class loaders to be able to create the appropriate Java proxies.
We have introduced Windows and Mac/Linux binaries for running several CLI tools. You no longer need to refer to the docs with extra-long options. You can now use the provided binaries to call the appropriate CLI tool.
If you use the quick installer, all these binaries will be installed for you.
Note that the bx-compat-cfml
module will take care of implementing .
createDynamicProxy
bif to support the request class loader so it can load classes from loaded libraries in the application.bx, runtime and more.bxCFTranspiler
, bxCompiler
, bxFeatureAudit
tools in the distribution bin folderRefactor JDBC connection retrieval out of the QueryOptions class
Dynamic method matching discovery algorithms updated to do 2 pass algorithm: exact, loose coercion matching
Improvement of cache service and cache provider methods for easier boxlang interactions
Refactored the dump css to `resources/dump/html/Dump.css`
Migrate dynamic proxies to native java implementation from the JDK
passing the session id to the onsessionstart listener
Give better warnings if the sessionStorage is not a valid string
attributecollection not handled properly on cfthrow
Left in system out calls that need to be removed
JSR ScriptEngine starting runtime without debug flag if passed
Creating a default cache was not setting the right name and a "default" already registered exception was being thrown
Default argument values not always checked for type
Implements missing from Box Class metadata
Static Scope missing from metadata