# Types & Scopes Each configuration binder has two public properties accessible in the `this` scope: 1. `this.TYPES` : A reference to `wirebox.system.ioc.Types` used to declare what type of object you are registering for construction or wiring 2. `this.SCOPES` : A reference to `wirebox.system.ioc.Scopes` used to declare in what life cycle scope the object will be stored under These two classes contain static public members in the this scope that facilitate the declaration of persistence scopes and construction types for object mappings. Both BoxLang (`.bx`) and CFML (`.cfc`) components are supported in all type declarations. Below are the valid enumerations for these two classes: **this.TYPES** * `CFC` : Construction of a CFC * `JAVA` : Construction of a Java class * `WEBSERVICE` : Construction of a webservice object * `RSS` : Construction of an RSS feed * `DSL` : Construction by DSL string * `CONSTANT` : A constant value * `FACTORY` : Construction by factory method * `PROVIDER` : Construction by a provider object or closure **this.SCOPES** * `NOSCOPE` : Transient objects * `PROTOTYPE` : Transient objects * `SINGLETON` : Objects constructed only once and stored in the injector * `SESSION` : ColdFusion session scoped based objects * `APPLICATION` : ColdFusion application scope based objects * `REQUEST` : ColdFusion request scope based objects * `SERVER` : ColdFusion server scope based objects * `CACHEBOX` : CacheBox scoped objects --- # 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/configuration/configuring-wirebox/types-and-scopes.md?ask= ``` 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.