The dependencies DSL methods are mostly used to define dependencies and also to activate advanced features on target objects, such as runtime mixins, virtual inheritance, etc.
Note Please note that you can concatenate more than one of these methods calls to dictate multiple constructor arguments, setter methods, cf properties, and more.
Tells WireBox which constructor to call on the mapped object. By default if an object has an
Tells WireBox that this mapped object will skip the constructor call for it. By default WireBox always calls object constructors
Tells WireBox that the mapped object should be constructed and then wired with a strict concurrency lock for property injections, setter injections and onDIComplete(). Please be aware that if you use this mode of construction, circular dependencies are not allowed. The default is that property and setter injections and onDIComplete() are outside of the construction locks
Tells WireBox to construct objects by locking only the constructor and constructor argument dependencies to allow for circular dependencies. This is the default construction mode of all persisted objects: singleton, session, server, application and cachebox scope
Tells WireBox that this mapped object has its dependencies described programmatically instead of using metadata inspection to discover them
Tells WireBox that this mapped object has a parent mapping with definitions it should use to base it from. This feature provides a great way to reuse object mapping definitions
Used to define a constructor argument for the mapped object.
You can pass as many arguments (named or positional) to this method to simulate the
Used to define a factory method argument for the mapped object when using a factory method construction.
Used to define a property mixin that will occur at runtime.
Used to define all the setter dependencies for a mapped object that follows the JavaBean spec:
A UDF template, a list of templates or an array of templates that WireBox should use to mix-in into the target object. It will take all the methods defined in those UDF templates and mixed them into the target object at runtime.
Will inject a new method or override a method on the target object with a new method that provides objects of the mapping you specify.
Create a runtime virtual inheritance from a target object into a target mapping. This approach blends the CFCs together at runtime via mixins and WireBox Funkyness!
Allows the ability to store extra metadata about a mapping into WireBox that can later be retrieved via AOP invocations or WireBox events.
Influence the creation process of a single object. The instance is already built and then passed into the closure for additional influence. You can optionally return the object and it will override it.