Blog

Brad Wood

September 28, 2012

Spread the word


Share your thoughts

By default, WireBox will look for your CFCs using the "models" convention (scan location). So, if you ask WireBox to get you "Services.Security.PadLockService", WireBox will look for that path and component name in the root of the models directory and create a WireBox mapping for you.

If you want to reference that CFC as just "PadLockService" or an alias such as "MyReallySecureService", you can create an explicit mapping like so in your WireBox config:

map("PadLockService").to("models.Services.Security.PadLockService");
or
map("MyReallySecureService").to("models.Services.Security.PadLockService");

What if you have a ton of CFCs scattered about a bunch of sub-directories and you don't want to type out the DSL for all of them? Enter map Directory()! This handy function can be placed right in your config and it will instruct WireBox to recursively search through the directory you specify and create a mapping for every CFC it finds.

The following DSL will create a mapping for every component in "/models/Services" and all of its sub directories.

mapDirectory("models.Services");

WireBox gives you a lot of flexibility to get your components mapped, and mapDirectory() is a very handle tool to keep in your bag of tricks.

More info here: http://wiki.coldbox.org/wiki/WireBox.cfm#Mapping_Initiators

P.S. When using mapDirectory(), the mapping ID (what you use to auto wire that component later when you need to use it) will default to the name of the CFC. You can override that as well as other settings with annotations in the component declaration.

component name="PadLockService" alias="MyReallySecureService" {}

Add Your Comment

Recent Entries

TestBox: Write Better Tests, Build Better BoxLang & CFML Apps

TestBox: Write Better Tests, Build Better BoxLang & CFML Apps

Building reliable software isn’t just about writing good code it’s about proving it works, every single time. As applications grow in complexity, having a solid, expressive, and flexible testing framework becomes essential.

That’s where TestBox comes in.

Victor Campos
Victor Campos
February 13, 2026
BoxLang NeoVim Plugin Released

BoxLang NeoVim Plugin Released

We're excited to announce the release of the BoxLang NeoVim Plugin - a comprehensive syntax highlighting solution designed specifically for BoxLang developers working in Vim and NeoVim environments. This isn't a port or adaptation of existing CFML syntax files; it's a ground-up implementation built for BoxLang's modern feature set. Coming soon as well will be our runners, syntax validators, and integration with our LSP for live previews, insights, and much more.

Luis Majano
Luis Majano
February 13, 2026
Announcing Cloud-Native BoxLang for $5/Month

Announcing Cloud-Native BoxLang for $5/Month

TL;DR: We just released a production-ready starter template that deploys a modern BoxLang application to DigitalOcean App Platform in under 5 minutes—starting at just $5/month. One-click deployment, auto-scaling, automatic redeployments, and zero downtime included.

Luis Majano
Luis Majano
February 10, 2026