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

Speaker Featuring - Round 1

Speaker Featuring - Round 1

Every conference is more than the talks we see on stage it’s also the story of the people who make it possible.

With the first round of Into the Box 2026 sessions and workshops now live, we’re excited to introduce some of the speakers who will be joining us this year. These community members, practitioners, and Ortus team experts bring decades of real-world experience across CFML, BoxLang, JVM modernization, testing, AI, and cloud-native development.

Victor Campos
Victor Campos
January 26, 2026
First Round of the Into the Box 2026 Agenda Is Live

First Round of the Into the Box 2026 Agenda Is Live

Into the Box 2026 marks an important moment for the CFML and BoxLang community not just because of what’s on the agenda, but because of what it represents: 20 years of Ortus Solutions helping teams move forward, modernize, and build with confidence.

Victor Campos
Victor Campos
January 21, 2026
BoxLang AI v2: Enterprise AI Development Without the Complexity

BoxLang AI v2: Enterprise AI Development Without the Complexity

One Year. 100+ Features. Unlimited Possibilities.

Just one year ago, in March 2024, we launched BoxLang AI 1.0. Today, we're thrilled to announce BoxLang AI v2—a massive leap forward that positions BoxLang as the most powerful and versatile AI framework on the JVM.

Luis Majano
Luis Majano
January 19, 2026