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

A Year in Review - BoxLang 2024 Recap!

A Year in Review - BoxLang 2024 Recap!

BoxLang has come a long way since its beta release, and we're thrilled to share the incredible progress made so far. From its initial launch to the upcoming stable version, BoxLang has been evolving with new features, tools, and a growing ecosystem, all aimed at empowering modern developers.In this recap, we’ll highlight the milestones and advancements that have shaped BoxLang’s journey to this point. Let’s take a look at what we’ve achieved and what’s coming next!

Maria Jose Herrera
Maria Jose Herrera
January 03, 2025
Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

At Ortus Solutions, we’ve always been at the forefront of innovation in the ColdFusion ecosystem. From pioneering modern ColdFusion practices to developing cutting-edge tools and frameworks, we’ve been passionate to help and sup[port the community into shaping the future of web development.That’s why we decided to build BoxLang, our new JVM programming language that not only builds on the strengths of ColdFusion but takes modern software development to the next level.

Maria Jose Herrera
Maria Jose Herrera
December 23, 2024