Custom Providers
If you need to abstract old legacy code or have funky construction processes, we would recommend you build your own provider objects. This means that you will create a component that implements
wirebox.system.ioc.IProvider (one get() method) and then you can map it. Once mapped, you can use it anywhere WireBox listens for providers:- The Injection DSL →
1
property name="" inject="provider:{name or injectionDSL}";
Copied!
- The mapping DSL
1
map("MyCFC").toProvider('name or injectionDSL')
2
​
3
// or
4
setter,property,methodArg,initArg(name="",dsl="provider:{name or injectionDSL}");
Copied!
Here is the interface you need to implement:
1
<cfinterface hint="The WireBox Provider Interface that follows the provider pattern">
2
<--- get --->
3
<cffunction name="get" output="false" access="public" returntype="any" hint="Get the provided object">
4
</cffunction>
5
</cfinterface>
Copied!
The CFC you build will need to be mapped so it can be retrieved by name and also so if it needs DI or any other WireBox funkiness, it can get it. So let's look at our FunkyEspressoProvider that we needed to create since we have some old legacy machines that we need to revamp:
1
component name="FunkyEspressoProvider" implements="coldbox.system.ioc.IProvider" singleton{
2
​
3
property name="log" inject="logbox:logger:FunkyEspressoProvider";
4
​
5
public function init(){ return this; }
6
​
7
Espresso public function get(){
8
// log
9
log.canDebug(){ log.debug("Requested funky espresso"); }
10
var espresso = createObject("component","old.legacy.Espresso").init();
11
// add some sugar as the old legacy machine is not that great.
12
espresso.addSugar(1);
13
// returned provided object.
14
return espresso;
15
}
16
​
17
}
Copied!
Finally we map to the provider using the
.toProvider() mapping method in the binder so anytime somebody requests an Espresso we can get it from our funky provider. Please note that I also map the provider because it also has some DI needed.1
component extends="coldbox.system.ioc.config.Binder"{
2
function configure(){
3
// map the provider first, so it can be constructed and DI performed on it.
4
map("FunkyEspressoProvider")
5
.to("model.legacy.FunkyEspressoProvider");
6
​
7
// map espresso's to the old funky provider for construction and retrieval.
8
map("Espresso")
9
.toProvider("FunkyEspressoProvider");
10
​
11
}
12
}
Copied!
Cool! That's it, anytime you request an
Espresso, WireBox will direct its construction to the provider you registered it with.Copy link
Edit on GitHub