# WireBox Injector

![](/files/-MOlsm00Zhe9Gj3DLD1Q)

WireBox bases itself on the idea of creating object injectors (`wirebox.system.ioc.Injector`) that in turn will produce and wire all your objects. You can create as many injector instances as you like in your applications, each with configurable differences or be linked hierarchically by setting each other as parent injectors.

Each injector can be configured with a configuration binder or none at all. If you are a purely annotations based kind of developer and don't mind requesting pathed components by convention, then you can use the no-configuration approach and not even have a single configuration file, all using autowiring and discovery of conventions. However, if you would like to alter the behavior of the injector and also create object mappings, you will need a configuration binder. The next section explains the way to create this configuration binder, below is how to startup or bootstrap the injector in different manners:

**No Configuration Binder:**

```javascript
myObject = new coldbox.system.ioc.Injector().getInstance("my.object");
```

**With a Configuration Binder:**

```javascript
myObject = new coldbox.system.ioc.Injector("myBinderPath").getInstance("CoolObject");
```

The WireBox injector class is the pivotal class that orchestrates DI, instance events and so much more. We really encourage you to study its [API Docs](http://www.coldbox.org/api) to learn more about its construction and usage methods.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wirebox.ortusbooks.com/2/usage/wirebox-injector.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.