BoxLang 🚀 A New JVM Dynamic Language Learn More...
Copyright Since 2005 ColdBox Platform by Luis Majano
and Ortus Solutions, Corp
www.coldbox.org | www.ortussolutions.com
This module allows your ColdBox applications to class load different
Java classes and libraries at runtime. On Adobe ColdFusion and Lucee
it uses the bundled JavaLoader project. On BoxLang 1.8.0+ it uses
BoxLang's native request class loader while keeping the same
loader@cbjavaloader facade and javaloader:
WireBox DSL.
Apache License, Version 2.0.
loader@cbjavaloader
mapping and the javaloader: DSL.Just drop into your modules folder or use the box-cli to install
box install cbjavaloader
The module has a default folder called lib where any
jars you drop there will be class loaded automatically. However, we
recommend using the loadpaths setting for selecting an
array of locations to class load, so when the module updates you won't
lose those files.
On BoxLang 1.8.0+, those configured paths are added to the native request class loader. On Adobe ColdFusion and Lucee, they continue to be loaded through JavaLoader.
box install cbjavaloader.moduleSettings.cbJavaLoader.loadPaths in
your app's ColdBox.cfc.loader@cbjavaloader or use inject="javaloader:YourClass".create( "YourClass" ) and initialize
your Java object as needed.The module registers the following mapping in WireBox:
loader@cbjavaloader. This is the facade you will use to
class load, append paths, and inspect the active class loader. The
main methods are:
create( class ) - Create a loaded Java classappendPaths( dirPath, filter ) - Appends a directory
path of *.jar or *.class files to the
current class loader.getLoadedURLs() - Get all the loaded URLsgetURLClassLoader() - Get the active class loader implementationgetVersion() - Get the JavaLoader facade versionloader@cbjavaloader uses the native
request class loader. setup() and
appendPaths() call addPaths(), and
create() resolves classes with createObject(
"java", className, getRequestClassLoader() ).cfcdynamicproxy.jar support jar.getLoadedURLs() will
usually report fewer entries on BoxLang than on Adobe ColdFusion or
Lucee for the same configuration.The module also registers a new WireBox DSL called
javaloader. You can then use this custom DSL for
injecting Java classes easily:
property name="name" inject="javaloader:{class-path}";
property name="hello" inject="javaloader:HelloWorld";
property name="buffer" inject="javaloader:org.class.path.StringBuffer";
Here are the module settings you can place in your
ColdBox.cfc under an
moduleSettings.cbJavaLoader structure:
moduleSettings = {
cbJavaLoader = {
// A single path, and array of paths or a single Jar
loadPaths = [],
// Load ColdFusion classes with loader (JavaLoader runtimes only)
loadColdFusionClassPath = false,
// Attach a custom class loader as a parent (JavaLoader runtimes only)
parentClassLoader = "",
// Directories that contain Java source code that are to be dynamically compiled (JavaLoader runtimes only)
sourceDirectories = [],
// the directory to build the .jar file for dynamic compilation in, defaults to ./tmp (JavaLoader runtimes only)
compileDirectory = "models/javaloader/tmp",
// Whether or not the source is trusted, i.e. it is going to change? Defaults to false, so changes will be recompiled and loaded (JavaLoader runtimes only)
trustedSource = false
}
};
In BoxLang native mode, loadPaths is the primary setting
used by the loader facade. The remaining compilation and parent-loader
settings continue to apply to the JavaLoader-backed Adobe ColdFusion
and Lucee path.
tools.jar / JDK
compiler availability).loadPaths
entries point to valid jars or directories.getLoadedURLs() to inspect what the active class
loader has loaded at runtime.Below is a simple example:
/**
* My Event Handler Hint
*/
component{
// Inject JavaLoader
property name="javaloader" inject="loader@cbjavaloader";
// Index
any function index( event,rc, prc ){
// create a java class
prc.hello = javaloader.create( "HelloWorld" ).init().hello();
}
// Run on first init
any function onAppInit( event, rc, prc ){
// on application start, load up more jars
javaloader.appendPaths( getSetting( "ApplicationPath" ) & "jars" );
}
}
Copyright Since 2005 ColdBox Framework by Luis Majano and Ortus Solutions, Corp www.ortussolutions.com
Because of His grace, this project exists. If you don't like this, then don't read it, its not for you.
"Therefore being justified by faith, we have peace with God through our Lord Jesus Christ: By whom also we have access by faith into this grace wherein we stand, and rejoice in hope of the glory of God. And not only so, but we glory in tribulations also: knowing that tribulation worketh patience; And patience, experience; and experience, hope: And hope maketh not ashamed; because the love of God is shed abroad in our hearts by the Holy Ghost which is given unto us. ." Romans 5:5
"I am the way, and the truth, and the life; no one comes to the Father, but by me (JESUS)" Jn 14:1-12
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
loader@cbjavaloader now skips JavaLoader initialization on BoxLang and loads configured loadPaths directly into the native request class loader.cfcdynamicproxy.jar, so getLoadedURLs() differs from Adobe CF and Lucee runtimes.setup-commandbox command to avoid having the box.zip included in the reposerver-*.json files on the final buildtags directory
$
box install cbjavaloader